Skip to content

💫 Toolkit to help you get started with SDD or any other process!

docs: target Windows PowerShell 5.1 (#4973)

Manfred Riemc4ac84168b63
diff --git a/AGENTS.md b/AGENTS.md
index 949f4999f..1ab4e0aa5 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -44,6 +44,16 @@ an LLM, read
Behavioral changes need positive and negative coverage; bug fixes need
before-and-after regression evidence.
+## PowerShell Compatibility
+
+All PowerShell scripts in the repository and all generated PowerShell
+functionality MUST target Windows PowerShell 5.1, the version included with
+Windows. When adding or changing PowerShell code, use only syntax, cmdlets,
+parameters, and .NET APIs available in Windows PowerShell 5.1. Account for
+encoding and other runtime differences, preserve the required behavioral
+parity with Bash and Python implementations, and provide Windows PowerShell
+5.1 validation evidence for behavioral changes.
+
## Branches and Agent Contributions
When creating a branch, follow [Branch naming](CONTRIBUTING.md#branch-naming).
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index c264d0f99..346fb24f3 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -234,6 +234,13 @@ core scripts, extensions, presets, and tooling; workflow step types; and
execution wiring such as script selection, workflow shell steps, and CI `run:`
steps. Existing tests count when they cover the changed behavior.
+Behavioral changes to repository-maintained or generated PowerShell
+functionality must include evidence from Windows PowerShell 5.1 or reproducible
+evidence that demonstrates 5.1 compatibility. All PowerShell scripts in the
+repository and all generated PowerShell functionality MUST target Windows
+PowerShell 5.1. Check syntax, cmdlet and parameter availability, .NET Framework
+APIs, encoding, and process/runtime behavior against that target.
+
Bug fixes also need a regression test that fails before the fix and passes
afterward. If a baseline or an execution path cannot be tested automatically,
explain the limitation and provide reproducible evidence for the affected
diff --git a/design/integration.md b/design/integration.md
index b110bbafc..04509705d 100644
--- a/design/integration.md
+++ b/design/integration.md
@@ -72,6 +72,14 @@ Core templates that call scripts declare `sh`, `ps`, and `py` commands in
`scripts:` frontmatter; template processing replaces `{SCRIPT}` with the
selected variant. `py` is opt-in; non-interactive init defaults to `sh` on
POSIX or `ps` on Windows. Maintain equivalent stdout behavior across all three.
+All PowerShell scripts in the repository and all PowerShell functionality
+generated from repository templates MUST target Windows PowerShell 5.1. All
+such code must use only language features, cmdlets, parameters, and runtime
+APIs available in Windows PowerShell 5.1. Implementations must also account for
+encoding, .NET Framework, and process/runtime differences in Windows
+PowerShell 5.1 while preserving the required Bash and Python behavioral parity.
+Validation evidence for behavioral PowerShell changes must exercise Windows
+PowerShell 5.1 or otherwise demonstrate 5.1 compatibility.
Bundled extension commands do not yet use this core-template script routing.
`__AGENT__` and command references are resolved during rendering, not by
adding per-agent wrapper scripts. For `generic`, extension registration