Menu
Repair PowerShell relative-path display helpers so Windows and Linux/macOS keep project-relative bootstrap paths truthful
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Perform a Specrew human-verdict boundary stop on the Claude host. Renders the FULL Rule 46 six-section human re-entry packet AND the verdict options as one Markdown message, with the AskUserQuestion picker disabled so the packet cannot collapse into the picker's short header/option fields. Invoke at EVERY human-judgment boundary stop (specify, clarify, plan, tasks, before-implement, implement, review, retro, feature-closeout, lifecycle-end). Triggers: boundary stop, verdict, approve / redirect / send back, why I stopped, human re-entry packet, gate stop.
{what this skill teaches agents}
Run Specrew's per-lens design workshop and collaborative design-analysis. Use whenever you work the design lenses for a feature: at specify/intake (the lens workshop) and at the design-analysis stop (co-design the architecture), and RE-INVOKE at the start of EACH new lens (architecture, data, ui-ux, security, integration, devops, requirements/NFR, observability, component). Triggers: design, design lens, lens workshop, design-analysis, architecture, trade-offs, co-design, explore options, decompose, or moving from one lens to the next. Tells you to facilitate each lens as a discussion, surface diagrams the human can actually SEE (console ASCII inline; mermaid/html to a file with a clickable file:/// link), co-design components/responsibilities/flows WITH the human instead of handing over finished options, capture the agreements, and which per-lens md to load.
| name | powershell-cross-platform-display-paths |
| description | Repair PowerShell relative-path display helpers so Windows and Linux/macOS keep project-relative bootstrap paths truthful |
| domain | powershell |
| confidence | high |
| source | earned |
| tools | [{"name":"view","description":"Inspect helper functions that trim or render project-relative paths","when":"When auditing PowerShell scripts for cross-platform path display bugs"},{"name":"powershell","description":"Run focused integration scripts after helper changes","when":"When validating Windows regressions while repairing Linux/macOS path handling"}] |
Use this when a PowerShell CLI renders project-relative file references for humans or downstream tools and the code was originally written with Windows-only separator assumptions.
