Use `AGENTS.md` for the repo-local maintenance flow, `PLANS.md` for the standing ExecPlan rules, and `plan.md` as the current worked example when you need a living plan. Use `docs/sysadmin-main-multi-agent-sop.md` for extended notes. Use `docs/windows-sandbox-validation.md` for both the disposable manual Sandbox shell and the automated `-WhatIf` capture wrapper. Keep the repo-local entrypoints and `.github/workflows/powershell-validation.yml` aligned when the validation flow changes.
Resources
8Install
npx skillscat add padtgit/script-powershell-7 Install via the SkillsCat registry.
Script.Powershell.7 Skill Entry
Use the canonical script tree under PowerShell Script/, with PowerShell Script/V7/ as the preferred maintained surface for migrated scripts.
Core Rules
- This checkout tracks
originPadtGit/Script.Powershell.7on branchmain. PowerShell Script/*is the primary implementation surface, andPowerShell Script/V7/*is the default target for maintained high-risk scripts.- Use
PLANS.mdfor the standing repo-local ExecPlan rules andplan.mdfor the current worked example when a task needs a living execution plan. - Current V7 maintained scripts include:
PowerShell Script/V7/windows-maintenance/Reset.Network.RebootPC.ps1,PowerShell Script/V7/windows-maintenance/Move-OrphanedInstallerFiles.ps1,PowerShell Script/V7/windows-maintenance/Nettoyage.Avance.Windows.Sauf.logserreur.ps1,PowerShell Script/V7/Printer/Restart.Spool.DeletePrinterQSimple.ps1,
andPowerShell Script/V7/Printer/restart.SpoolDeleteQV4.ps1. - Preserve existing
Set-StrictMode,$ErrorActionPreference, andSupportsShouldProcessbehavior unless the task explicitly changes them. - Preserve usable
-WhatIfbehavior wherever a script already supports safe preview without elevation. - Write generated validation output to
artifacts/validation/, not tracked repo files. - Treat
sysadmin-mainin runtime paths as a stable storage label, not a repo name.
Validation Entry Points
- Root validator:
Invoke-WhatIfValidation.ps1 - Pester tests:
tests/ - Analyzer runner:
pwsh -NoProfile -ExecutionPolicy Bypass -File '.\tools\Invoke-PSScriptAnalyzer.ps1' -Path . -Recurse -SettingsPath '.\tools\PSScriptAnalyzerSettings.psd1' -EnableExit -ExitCodeMode AllDiagnostics - CI validation runner:
pwsh -NoProfile -ExecutionPolicy Bypass -File '.\tools\Invoke-CIValidation.ps1' - Sandbox launcher:
Start-Process '.\sandbox\sysadmin-main-validation.wsb' - Automated sandbox
-WhatIflauncher:Start-Process '.\artifacts\validation\sandbox-whatif-validation.wsb' - Sandbox output sync:
& "$env:SystemRoot\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy Bypass -File '.\artifacts\validation\Copy-SandboxWhatIfOutput.ps1'
Detailed Workflow
Use AGENTS.md for the repo-local maintenance flow, PLANS.md for the standing ExecPlan rules, and plan.md as the current worked example when you need a living plan. Use docs/sysadmin-main-multi-agent-sop.md for extended notes. Use docs/windows-sandbox-validation.md for both the disposable manual Sandbox shell and the automated -WhatIf capture wrapper. Keep the repo-local entrypoints and .github/workflows/powershell-validation.yml aligned when the validation flow changes.