prizmkit 1.1.70 → 1.1.74

package/bundled/dev-pipeline-windows/templates/sections/phase-browser-verification.md

@@ -1,62 +1,168 @@
 ### Browser Verification (playwright-cli) — MANDATORY
 
-You MUST execute this phase with `playwright-cli`. Use native PowerShell commands for setup, server lifecycle, and cleanup.
+You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without actually running playwright-cli.
 
-**Readiness**:
+**Using: playwright-cli**
+
+**CRITICAL CONSTRAINT — playwright-cli ONLY, NO Playwright MCP**:
+- You MUST use `playwright-cli` (the CLI tool) for ALL browser interactions in this phase
+- **NEVER** use Playwright MCP server, Playwright MCP tools, or any MCP-based browser automation
+- If you have Playwright MCP configured, IGNORE it entirely — use the CLI command `playwright-cli` exclusively
+- All browser actions go through `playwright-cli <command>` in the PowerShell tool, not through any MCP tool call
+
+**Step 0 — Playwright CLI Readiness Check (BLOCKING — must pass before any browser action)**:
+
+0a. Check if `playwright-cli` is installed:
 ```powershell
 $playwright = Get-Command playwright-cli -ErrorAction SilentlyContinue
-if ($playwright) { playwright-cli --version } else { "PLAYWRIGHT_CLI:NOT_INSTALLED" }
+if ($playwright) { playwright-cli --version } else { "NOT_INSTALLED" }
 ```
-
-If playwright-cli is not available, install it:
+If output is `NOT_INSTALLED`, install it:
 ```powershell
 npm install -g @playwright/cli@latest
+```
+Then verify installation succeeded:
+```powershell
 playwright-cli --version
 ```
+If installation fails, log the error in context-snapshot.md under `## Browser Verification: SKIPPED — playwright-cli installation failed` and proceed to the next phase. Do NOT attempt browser verification without playwright-cli.
 
-**Dev server setup**:
+0b. Learn playwright-cli usage (run once per session to understand available commands):
 ```powershell
-$DEV_PORT = "{{DEV_PORT}}"
-if ($DEV_PORT -eq "{{DEV_PORT}}") {
-  $detected = node -e "const p=require('./package.json'); const s = p.scripts ? p.scripts.dev : ''; const m=s.match(/-p\s+(\d+)/); console.log(m?m[1]:'')"
-  if ($detected) { $DEV_PORT = $detected } else { $DEV_PORT = "3000" }
-}
-"Detected DEV_PORT=$DEV_PORT"
-$portBusy = Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue
-if ($portBusy) { "PORT_IN_USE" } else { "PORT_FREE" }
-$server = Start-Process -FilePath "powershell" -ArgumentList @("-NoProfile", "-Command", "<start-command>") -PassThru
-$DEV_SERVER_PID = $server.Id
+playwright-cli --help
 ```
+Use this output to determine the correct commands for your verification steps. Do NOT guess command syntax — refer to the help output.
 
-Wait for readiness:
+0c. Check if playwright-cli skill is installed for the current AI platform:
+```powershell
+$currentPlatform = "unknown"
+$skillDir = $null
+if (Get-Command claude -ErrorAction SilentlyContinue) {
+  $currentPlatform = "claude"
+  $skillDir = Join-Path $HOME ".claude\skills"
+} elseif (Get-Command cbc -ErrorAction SilentlyContinue) {
+  $currentPlatform = "codebuddy"
+  $skillDir = Join-Path $HOME ".cbc\skills"
+}
+
+$skillExists = $false
+if ($skillDir) {
+  $directSkill = Join-Path $skillDir "playwright-cli"
+  $matchingSkills = Get-ChildItem -Path $skillDir -Filter "playwright*" -ErrorAction SilentlyContinue
+  $skillExists = (Test-Path -LiteralPath $directSkill) -or [bool]$matchingSkills
+}
+if ($skillExists) { "SKILL_EXISTS" } else { "SKILL_MISSING" }
+```
+If `SKILL_MISSING`:
+```powershell
+playwright-cli install --skills
+```
+If the current platform is NOT claude, move the installed skill files to the correct location:
 ```powershell
-$ready = $false
-for ($i = 0; $i -lt 15; $i++) {
-  try {
-    $response = Invoke-WebRequest -Uri "http://localhost:$DEV_PORT" -UseBasicParsing -TimeoutSec 2
-    if ($response.StatusCode -in @(200, 302)) { $ready = $true; break }
-  } catch { Start-Sleep -Seconds 2 }
+$claudeSkillDir = Join-Path $HOME ".claude\skills"
+$sourceSkill = Join-Path $claudeSkillDir "playwright-cli"
+if ($currentPlatform -ne "claude" -and $currentPlatform -ne "unknown" -and $skillDir -and (Test-Path -LiteralPath $sourceSkill)) {
+  New-Item -ItemType Directory -Force -Path $skillDir | Out-Null
+  Copy-Item -Recurse -Force -Path $sourceSkill -Destination $skillDir
+  "Moved playwright-cli skill from claude to $currentPlatform"
 }
-if (-not $ready) { "DEV_SERVER_NOT_READY" }
 ```
 
-**Verification goals**:
+0d. Read the installed playwright-cli skill for workflow guidance:
+After skill installation, read the skill's SKILL.md to understand recommended workflows and patterns. Use these patterns to construct your verification flow — do NOT invent your own patterns if the skill provides them.
+
+**Step 1 — Start Dev Server**:
+
+You know this project's tech stack. Detect and start the dev server yourself:
+
+1. Identify the dev server start command from project config (`package.json` scripts, `Makefile`, `docker-compose.yml`, etc.)
+2. **Detect the dev server port** — use the pre-detected port from pipeline if available, otherwise extract from project config. Do NOT hardcode or guess the port:
+   ```powershell
+   $DEV_PORT = "{{DEV_PORT}}"
+   if ($DEV_PORT -eq "{{DEV_PORT}}" -or [string]::IsNullOrWhiteSpace($DEV_PORT)) {
+     $detectedPort = ""
+     if (Test-Path -LiteralPath "package.json") {
+       $detectedPort = node -e "const p=require('./package.json'); const s=(p.scripts?.dev) || ''; const m=s.match(/-p\s+(\d+)/); console.log(m?m[1]:'')"
+     }
+     if (-not $detectedPort -and $env:NEXT_PUBLIC_SITE_URL -match ':([0-9]+)') {
+       $detectedPort = $Matches[1]
+     }
+     if ($detectedPort) { $DEV_PORT = $detectedPort } else { $DEV_PORT = "3000" }
+   }
+   "Detected DEV_PORT=$DEV_PORT"
+   ```
+3. Verify the port is available and start the dev server in the background, capturing its process id:
+   ```powershell
+   $portBusy = Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue
+   if ($portBusy) { "PORT_IN_USE" } else { "PORT_FREE" }
+   $devServerCommand = "<start-command>"
+   $server = Start-Process -FilePath "powershell" -ArgumentList @("-NoProfile", "-Command", $devServerCommand) -PassThru
+   $DEV_SERVER_PID = $server.Id
+   ```
+
+   Wait for server to be ready: poll `http://localhost:$DEV_PORT` until it returns 200 or 302 (max 30 seconds, 2s interval):
+   ```powershell
+   $ready = $false
+   for ($i = 0; $i -lt 15; $i++) {
+     try {
+       $response = Invoke-WebRequest -Uri "http://localhost:$DEV_PORT" -UseBasicParsing -TimeoutSec 2
+       if ($response.StatusCode -in @(200, 302)) { $ready = $true; break }
+     } catch {
+       Start-Sleep -Seconds 2
+     }
+   }
+   if (-not $ready) { "DEV_SERVER_NOT_READY" }
+   ```
+4. Open the app in playwright-cli: `playwright-cli open "http://localhost:$DEV_PORT"`
+5. If the page requires authentication, use playwright-cli to register a test user and log in first
+
+**Step 2 — Verification**:
+
+Use `playwright-cli snapshot` on the running app to discover actual element refs, then verify these goals:
 {{BROWSER_VERIFY_STEPS}}
 
-Use `playwright-cli open http://localhost:$DEV_PORT`, `playwright-cli snapshot`, interaction commands from `playwright-cli --help`, and `playwright-cli screenshot`.
+Construct your verification workflow based on:
+1. The playwright-cli skill documentation (read in Step 0d)
+2. The `playwright-cli --help` output (captured in Step 0b)
+3. The current task's Verification Gates and implemented features
 
-**Cleanup**:
-```powershell
-playwright-cli close
-if ($DEV_SERVER_PID) { Stop-Process -Id $DEV_SERVER_PID -Force -ErrorAction SilentlyContinue }
-Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue |
-  Select-Object -ExpandProperty OwningProcess -Unique |
-  ForEach-Object { Stop-Process -Id $_ -Force -ErrorAction SilentlyContinue }
+Decide the concrete playwright-cli actions (click, fill, snapshot, screenshot, etc.) yourself based on the snapshot output and your knowledge of the implemented code. The goals above describe WHAT to verify — you determine HOW using playwright-cli commands.
+
+Take a final screenshot for evidence: `playwright-cli screenshot`
+
+**Step 3 — Cleanup (REQUIRED — you started it, you stop it)**:
+
+1. Close the playwright-cli browser: `playwright-cli close`
+2. Stop the dev server process and any remaining process bound to the dev server port:
+   ```powershell
+   if ($DEV_SERVER_PID) { Stop-Process -Id $DEV_SERVER_PID -Force -ErrorAction SilentlyContinue }
+   Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue |
+     Select-Object -ExpandProperty OwningProcess -Unique |
+     ForEach-Object { Stop-Process -Id $_ -Force -ErrorAction SilentlyContinue }
+   ```
+
+**Step 4 — Reporting**:
+
+Append results to `context-snapshot.md`:
+```
+## Browser Verification
+Tool: <playwright-cli or opencli>
+URL: http://localhost:$DEV_PORT
+Dev Server Command: <actual command used>
+Tool version: <version>
+Steps executed: [list of commands used]
+Screenshot: [path]
+Result: PASS / FAIL (reason)
+Server cleanup: confirmed
+Browser cleanup: confirmed
 ```
 
-Append results to `context-snapshot.md` with URL, command used, playwright-cli version, steps executed, screenshot path, PASS/FAIL reason, and cleanup status.
+If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
 
-**Checkpoint update**:
+**Checkpoint update**: Run the update script to set step `browser-verification` to `"completed"`:
 ```powershell
-Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py --checkpoint-path {{CHECKPOINT_PATH}} --step browser-verification --status completed
+Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
+  --checkpoint-path {{CHECKPOINT_PATH}} `
+  --step browser-verification `
+  --status completed
 ```

package/bundled/dev-pipeline-windows/templates/sections/phase-commit-full.md

@@ -2,7 +2,7 @@
 
 **a.** Check if feature already committed:
 ```powershell
-git log --oneline | Select-String "{{FEATURE_ID}}" | Select-Object -First 3
+git log --oneline | Select-String -Pattern "{{FEATURE_ID}}" | Select-Object -First 3
 ```
 - If a commit for `{{FEATURE_ID}}` already exists → **skip d** (do NOT run /prizmkit-committer, do NOT run git reset, do NOT stage or unstage anything). Proceed directly to e Final verification.
 - If no existing commit → proceed normally with b–d.
@@ -30,7 +30,7 @@ This single commit includes: feature code + tests + .prizmkit/prizm-docs/ update
 ```powershell
 git status --short
 ```
-Working tree MUST be clean after this step. If any feature-related files remain, stage them into the SAME commit via `git add <file>; git commit --amend --no-edit`, do NOT create a separate commit.
+Working tree MUST be clean after this step. If any feature-related files remain, stage them into the SAME commit via `git add <file>; if ($LASTEXITCODE -eq 0) { git commit --amend --no-edit }`, do NOT create a separate commit.
 
 **f.** Write completion summary for downstream dependency context:
 
@@ -69,3 +69,14 @@ Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
   --step prizmkit-committer `
   --status completed
 ```
+
+### TERMINAL STOP — S09 Completed
+
+After all of the following are true, the session is **TERMINAL**:
+
+- `/prizmkit-committer` has completed
+- `git status --short` is clean (except ignored/local-only pipeline artifacts)
+- `.prizmkit/specs/{{FEATURE_SLUG}}/completion-summary.json` is written
+- the S09 / `prizmkit-committer` checkpoint is marked `completed`
+
+At that point, stop immediately. Do **not** process delayed teammate/reviewer findings, do **not** edit files, do **not** amend the commit, and do **not** start any new tool calls. Any findings that arrive after S09 is completed are follow-up work for a later session, not part of this feature commit.

package/bundled/dev-pipeline-windows/templates/sections/phase-commit.md

@@ -23,7 +23,7 @@ This single commit includes: feature code + tests + .prizmkit/prizm-docs/ update
 ```powershell
 git status --short
 ```
-Working tree MUST be clean after this step. If any feature-related files remain, stage them into the SAME commit via `git add <file>; git commit --amend --no-edit`, do NOT create a separate commit.
+Working tree MUST be clean after this step. If any feature-related files remain, stage them into the SAME commit via `git add <file>; if ($LASTEXITCODE -eq 0) { git commit --amend --no-edit }`, do NOT create a separate commit.
 
 **e.** Write completion summary for downstream dependency context:
 
@@ -62,3 +62,14 @@ Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
   --step prizmkit-committer `
   --status completed
 ```
+
+### TERMINAL STOP — S09 Completed
+
+After all of the following are true, the session is **TERMINAL**:
+
+- `/prizmkit-committer` has completed
+- `git status --short` is clean (except ignored/local-only pipeline artifacts)
+- `.prizmkit/specs/{{FEATURE_SLUG}}/completion-summary.json` is written
+- the S09 / `prizmkit-committer` checkpoint is marked `completed`
+
+At that point, stop immediately. Do **not** process delayed teammate/reviewer findings, do **not** edit files, do **not** amend the commit, and do **not** start any new tool calls. Any findings that arrive after S09 is completed are follow-up work for a later session, not part of this feature commit.

package/bundled/dev-pipeline-windows/templates/sections/phase-context-snapshot-agent-suffix.md

@@ -1,4 +1,4 @@
-   - **Section 3 — Prizm Context**: full content of root.prizm and relevant L1/L2 docs
+   - **Section 3 — Key TRAPS & RULES**: extract only relevant TRAPS/RULES from prizm-docs. Do NOT copy full L0/L1/L2 content — the orchestrator already loaded them.
    - **Section 4 — File Manifest**: For each file relevant to this feature, list: file path, why it's needed (modify/reference/test), key interface signatures (function names + params + return types). Do NOT include full file content — agents read files on-demand. Format:
      ### Files to Modify
      | File | Why Needed | Key Interfaces |

package/bundled/dev-pipeline-windows/templates/sections/phase-context-snapshot-base.md

@@ -1,24 +1,14 @@
 ### Build Context Snapshot
 
 ```powershell
-if (Test-Path .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md) { "EXISTS" } else { "MISSING" }
+if (Test-Path .prizmkit\specs\{{FEATURE_SLUG}}\context-snapshot.md) { "EXISTS" } else { "MISSING" }
 ```
 
 If MISSING — build it now:
 1. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 prizm docs
-2. Detect source code directories: read KEY_FILES and STRUCTURE sections from `root.prizm` to identify where source code lives (e.g. `src/`, `app/`, `lib/`, `cmd/`, `packages/`, or project root). If `root.prizm` is missing, scan the project tree:
-   ```powershell
-	   Get-ChildItem -Path . -File -Recurse -Depth 2 -Include *.js,*.ts,*.py,*.go,*.java,*.rb,*.rs -ErrorAction SilentlyContinue |
-	     Where-Object { $_.FullName -notmatch '\\(node_modules|\.git|dist|build|vendor)(\\|$)' } |
-	     Select-Object -First 30 -ExpandProperty FullName
-   ```
-   Identify the top-level source directories from the results.
-3. Scan the detected source directories for files related to this feature; read each one
-4. Write `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`:
-   - **Section 1 — Task Contract**: Objective, scope rule, non-scope rule, and Verification Gates from the Task Contract above
-   - **Section 2 — Project Structure**: run the following to get a visual directory tree, then paste output:
-     ```powershell
-	     Get-ChildItem -Path . -Directory -Recurse -Depth 2 -ErrorAction SilentlyContinue |
-	       Where-Object { $_.FullName -notmatch '\\(node_modules|\.git|dist|build|__pycache__|vendor)(\\|$)' } |
-	       Select-Object -ExpandProperty FullName
-     ```
+2. Read source files listed in the feature's scope (use prizm-docs KEY_FILES for guidance)
+3. Write `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`:
+   - **Section 1 — Feature Brief**: 2-3 line feature description from Task Contract
+   - **Section 2 — Verification Gates**: gate checklist from Task Contract
+   - **Section 3 — Key TRAPS & RULES**: extract only relevant TRAPS/RULES from prizm-docs that apply to files in this scope. Do NOT copy full L0/L1/L2 content.
+   - **Section 4 — File Manifest**: file path, why needed, key interfaces. Format: Files to Modify | Files for Reference tables.

package/bundled/dev-pipeline-windows/templates/sections/phase-context-snapshot-lite-suffix.md

@@ -1,6 +1,13 @@
-   - **Section 3 — Prizm Context**: content of root.prizm and relevant L1/L2 docs
-   - **Section 4 — Existing Source Files**: **full verbatim content** of each related file in fenced code blocks (with `### path/to/file` heading and line count). Include ALL files needed for implementation and review — downstream phases read this section instead of re-reading individual source files
-   - **Section 5 — Existing Tests**: full content of related test files as code block
+   - **Section 3 — Key TRAPS & RULES**: extract only relevant TRAPS/RULES from prizm-docs that apply to files in this scope. Do NOT copy full L0/L1/L2 content.
+   - **Section 4 — File Manifest**: For each relevant file, list path, why needed, key interface signatures. Use table format:
+
+     ### Files to Modify
+     | File | Why Needed | Key Interfaces |
+     |------|-----------|----------------|
+
+     ### Files for Reference
+     | File | Why Needed | Key Interfaces |
+     |------|-----------|----------------|
 
 
 **Checkpoint update**: Run the update script to set step `context-snapshot` to `"completed"`:

package/bundled/dev-pipeline-windows/templates/sections/phase-critic-plan-full.md

@@ -2,7 +2,7 @@
 
 **Guard**: Verify critic agent file exists before spawning:
 ```powershell
-if (Test-Path "{{CRITIC_SUBAGENT_PATH}}") { "CRITIC:READY" } else { "CRITIC:MISSING" }
+if (Test-Path -LiteralPath "{{CRITIC_SUBAGENT_PATH}}") { "CRITIC:READY" } else { "CRITIC:MISSING" }
 ```
 If CRITIC:MISSING — skip this phase entirely and proceed. Log: "Critic agent not installed — skipping Plan Challenge."
 

package/bundled/dev-pipeline-windows/templates/sections/phase-critic-plan.md

@@ -2,7 +2,7 @@
 
 **Guard**: Verify critic agent file exists before spawning:
 ```powershell
-if (Test-Path "{{CRITIC_SUBAGENT_PATH}}") { "CRITIC:READY" } else { "CRITIC:MISSING" }
+if (Test-Path -LiteralPath "{{CRITIC_SUBAGENT_PATH}}") { "CRITIC:READY" } else { "CRITIC:MISSING" }
 ```
 If CRITIC:MISSING — skip this phase entirely and proceed. Log: "Critic agent not installed — skipping Plan Challenge."
 

package/bundled/dev-pipeline-windows/templates/sections/phase-implement-agent.md

@@ -7,6 +7,7 @@
 |-----------|-------|
 | subagent_type | prizm-dev-team-dev |
 | run_in_background | false |
+| isolation | Leave empty — Dev works directly in the repo, no worktree |
 
 **Agent spawn failure policy**:
 - If spawning Dev fails with team/config/lock errors, retry at most once.
@@ -28,7 +29,8 @@ Wait for Dev to return. Implementation may proceed only when tasks are complete
 **Gate Check — Implementation Log**:
 After Dev agent returns, verify the Implementation Log was written:
 ```powershell
-if (Select-String -Path .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md -Pattern "## Implementation Log" -Quiet) { "GATE:PASS" } else { "GATE:MISSING" }
+$contextSnapshot = '.prizmkit\specs\{{FEATURE_SLUG}}\context-snapshot.md'
+if ((Test-Path $contextSnapshot) -and (Select-String -Path $contextSnapshot -Pattern '## Implementation Log' -Quiet)) { "GATE:PASS" } else { "GATE:MISSING" }
 ```
 If GATE:MISSING — send message to Dev (re-spawn if needed): "Write the '## Implementation Log' section to context-snapshot.md before I can proceed to review. Include: files changed/created, key decisions, deviations from plan, notable discoveries."
 

package/bundled/dev-pipeline-windows/templates/sections/phase-implement-full.md

@@ -4,7 +4,11 @@
 
 Before spawning Dev, check plan.md Tasks section:
 ```powershell
-Select-String -Pattern '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/plan.md 2>$null
+if (Test-Path -LiteralPath ".prizmkit/specs/{{FEATURE_SLUG}}/plan.md") {
+  (Select-String -Path ".prizmkit/specs/{{FEATURE_SLUG}}/plan.md" -Pattern '^- \[ \]' -ErrorAction SilentlyContinue).Count
+} else {
+  0
+}
 ```
 - If result is `0` (all tasks already `[x]`) → **SKIP this phase**, go directly to Review. Do NOT spawn Dev.
 - If result is non-zero → spawn Dev agent below.
@@ -33,12 +37,12 @@ Select-String -Pattern '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/plan.md 2>$n
 **Gate Check — Implementation Log**:
 After Dev agent returns, verify the Implementation Log was written:
 ```powershell
-if (Select-String -Path .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md -Pattern "## Implementation Log" -Quiet) { "GATE:PASS" } else { "GATE:MISSING" }
+if (Select-String -Path ".prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md" -Pattern "## Implementation Log" -Quiet -ErrorAction SilentlyContinue) { "GATE:PASS" } else { "GATE:MISSING" }
 ```
 If GATE:MISSING — send message to Dev (re-spawn if needed): "Write the '## Implementation Log' section to context-snapshot.md before I can proceed to review. Include: files changed/created, key decisions, deviations from plan, notable discoveries."
 
 Wait for Dev to return. **If Dev times out before all tasks are `[x]`**:
-1. Check progress: `Select-String -Pattern '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/plan.md`
+1. Check progress: `(Select-String -Path ".prizmkit/specs/{{FEATURE_SLUG}}/plan.md" -Pattern '^- \[ \]' -ErrorAction SilentlyContinue).Count`
 2. If any tasks remain: re-spawn Dev with this recovery prompt:
    > {{AGENT_PROMPT_DEV_RESUME}}
 3. Max 2 recovery retries. After 2 failures, orchestrator implements remaining tasks directly.

package/bundled/dev-pipeline-windows/templates/sections/phase-implement-lite.md

@@ -10,9 +10,7 @@
 You know this project's tech stack. Identify ALL test commands that apply (e.g., `go test ./...`, `npm test`, `cargo test`, `pytest`, `make test`, etc.). Record them as `TEST_CMDS`. Then record baseline:
 ```powershell
 # Run each test command, capture output
-& {
-  {{TEST_CMD}}
-} 2>&1 | Tee-Object (Join-Path $env:TEMP "test-baseline.txt") | Select-Object -Last 20
+& { {{TEST_CMD}} } 2>&1 | Tee-Object (Join-Path $env:TEMP "test-baseline.txt") | Select-Object -Last 20
 ```
 
 **3b.** Run `/prizmkit-implement` — this handles the full implementation cycle:

package/bundled/dev-pipeline-windows/templates/sections/phase-plan-agent.md

@@ -1,7 +1,7 @@
 ### Plan & Tasks
 
 ```powershell
-Get-ChildItem .prizmkit/specs/{{FEATURE_SLUG}}/plan.md -ErrorAction SilentlyContinue
+Test-Path -LiteralPath ".prizmkit/specs/{{FEATURE_SLUG}}/plan.md"
 ```
 
 If missing, run `/prizmkit-plan` with `artifact_dir=.prizmkit/specs/{{FEATURE_SLUG}}/` to generate `plan.md`:

package/bundled/dev-pipeline-windows/templates/sections/phase-plan-lite.md

@@ -1,7 +1,7 @@
 ### Plan & Tasks
 
 ```powershell
-Get-ChildItem .prizmkit/specs/{{FEATURE_SLUG}}/ -ErrorAction SilentlyContinue
+Get-ChildItem -LiteralPath ".prizmkit/specs/{{FEATURE_SLUG}}/" -ErrorAction SilentlyContinue
 ```
 
 If plan.md missing, run `/prizmkit-plan` with `artifact_dir=.prizmkit/specs/{{FEATURE_SLUG}}/`:

package/bundled/dev-pipeline-windows/templates/sections/phase-review-agent.md

@@ -7,7 +7,7 @@ The skill runs an internal review-fix loop (Reviewer Agent → filter → Dev Ag
 **Gate Check — Review Report**:
 After `/prizmkit-code-review` returns, verify the review report:
 ```powershell
-if (Select-String -Path .prizmkit/specs/{{FEATURE_SLUG}}/review-report.md -Pattern "## Verdict" -Quiet) { "GATE:PASS" } else { "GATE:MISSING" }
+if (Select-String -Path ".prizmkit/specs/{{FEATURE_SLUG}}/review-report.md" -Pattern "## Verdict" -Quiet -ErrorAction SilentlyContinue) { "GATE:PASS" } else { "GATE:MISSING" }
 ```
 If GATE:MISSING:
 - Do not re-run `/prizmkit-code-review` in an unbounded report-repair loop.

package/bundled/dev-pipeline-windows/templates/sections/phase-review-full.md

@@ -7,7 +7,7 @@ The skill runs an internal review-fix loop (Reviewer Agent → filter → Dev Ag
 **Gate Check — Review Report**:
 After `/prizmkit-code-review` returns, verify the review report:
 ```powershell
-if (Select-String -Path .prizmkit/specs/{{FEATURE_SLUG}}/review-report.md -Pattern "## Verdict" -Quiet) { "GATE:PASS" } else { "GATE:MISSING" }
+if (Select-String -Path ".prizmkit/specs/{{FEATURE_SLUG}}/review-report.md" -Pattern "## Verdict" -Quiet -ErrorAction SilentlyContinue) { "GATE:PASS" } else { "GATE:MISSING" }
 ```
 If GATE:MISSING:
 - Do not re-run `/prizmkit-code-review` in an unbounded report-repair loop.
@@ -19,7 +19,7 @@ Read `review-report.md` and check the Verdict:
 - `PASS` → proceed to next phase
 - `NEEDS_FIXES` → the skill exhausted its max rounds; log the remaining findings and proceed (do not retry externally)
 
-Run the full test suite: `({{TEST_CMD}}) 2>&1 | Tee-Object (Join-Path $env:TEMP "review-test-out.txt") | Select-Object -Last 20`
+Run the full test suite: `& { {{TEST_CMD}} } 2>&1 | Tee-Object (Join-Path $env:TEMP "review-test-out.txt") | Select-Object -Last 20`
 
 **CP-3**: Review complete, report written, and the Test Failure Recovery Protocol's Success Rule is satisfied.
 

package/bundled/dev-pipeline-windows/templates/sections/phase-specify-plan-full.md

@@ -2,7 +2,7 @@
 
 Check existing artifacts first:
 ```powershell
-Get-ChildItem .prizmkit/specs/{{FEATURE_SLUG}}/ -ErrorAction SilentlyContinue
+if (Test-Path .prizmkit\specs\{{FEATURE_SLUG}}) { Get-ChildItem .prizmkit\specs\{{FEATURE_SLUG}} | Select-Object -ExpandProperty Name } else { "MISSING" }
 ```
 
 - Both (spec.md, plan.md) exist → **SKIP to CP-1**
@@ -14,22 +14,17 @@ Get-ChildItem .prizmkit/specs/{{FEATURE_SLUG}}/ -ErrorAction SilentlyContinue
 1. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 prizm docs
 2. Detect source code directories: read KEY_FILES and STRUCTURE sections from `root.prizm` to identify where source code lives (e.g. `src/`, `app/`, `lib/`, `cmd/`, `packages/`, or project root). If `root.prizm` is missing, scan the project tree:
    ```powershell
-	   Get-ChildItem -Path . -File -Recurse -Depth 2 -Include *.js,*.ts,*.py,*.go,*.java,*.rb,*.rs -ErrorAction SilentlyContinue |
-	     Where-Object { $_.FullName -notmatch '\\(node_modules|\.git|dist|build|vendor)(\\|$)' } |
-	     Select-Object -First 30 -ExpandProperty FullName
+   Get-ChildItem -Path . -File -Recurse -Depth 2 -Include *.js,*.ts,*.py,*.go,*.java,*.rb,*.rs -ErrorAction SilentlyContinue |
+     Where-Object { $_.FullName -notmatch '\\(node_modules|\.git|dist|build|vendor)(\\|$)' } |
+     Select-Object -First 30 -ExpandProperty FullName
    ```
    Identify the top-level source directories from the results.
 3. Scan the detected source directories for files related to this feature; read each one
 4. Write `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`:
-   - **Section 1 — Task Contract**: Objective, scope rule, non-scope rule, and Verification Gates from the Task Contract above
-   - **Section 2 — Project Structure**: run the following to get a visual directory tree, then paste output:
-     ```powershell
-	     Get-ChildItem -Path . -Directory -Recurse -Depth 2 -ErrorAction SilentlyContinue |
-	       Where-Object { $_.FullName -notmatch '\\(node_modules|\.git|dist|build|__pycache__|vendor)(\\|$)' } |
-	       Select-Object -ExpandProperty FullName
-     ```
-   - **Section 3 — Prizm Context**: full content of root.prizm and relevant L1/L2 docs
-   - **Section 4 — File Manifest**: For each file relevant to this feature, list: file path, why it's needed (modify/reference/test), key interface signatures (function names + params + return types). Do NOT include full file content — agents read files on-demand. Format:
+   - **Section 1 — Feature Brief**: feature description (copy from Task Contract above, 2-3 lines only)
+   - **Section 2 — Verification Gates**: copy the gate checklist from the Task Contract above
+   - **Section 3 — Key TRAPS & RULES**: extract TRAPS and RULES entries from loaded prizm-docs that apply to files in this feature's scope. Do NOT copy full L0/L1/L2 content — only the specific TRAPS/RULES lines relevant to the files listed in Section 4.
+   - **Section 4 — File Manifest**: For each file relevant to this feature, list path, why needed (modify/reference/test), key interface signatures. Do NOT include full file content. Format:
      ### Files to Modify
      | File | Why Needed | Key Interfaces |
      |------|-----------|----------------|
@@ -42,21 +37,22 @@ Get-ChildItem .prizmkit/specs/{{FEATURE_SLUG}}/ -ErrorAction SilentlyContinue
 
      ### Known TRAPS (from .prizmkit/prizm-docs/)
      - <trap entries extracted from L1/L2 docs>
-   - **Section 5 — Existing Tests**: full content of related test files as code blocks
-5. Confirm: `ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`
+5. Confirm with PowerShell: `if (Test-Path .prizmkit\specs\{{FEATURE_SLUG}}\context-snapshot.md) { "EXISTS" } else { "MISSING" }`
 
 **After Step A**: Use context-snapshot.md Section 4 File Manifest to guide targeted file reads. Do NOT scan directories or read unrelated files.
 
 **Step B — Planning Artifacts** (generate only missing files):
 
 ```powershell
-Get-ChildItem .prizmkit/specs/{{FEATURE_SLUG}}/spec.md .prizmkit/specs/{{FEATURE_SLUG}}/plan.md -ErrorAction SilentlyContinue
+@('.prizmkit\specs\{{FEATURE_SLUG}}\spec.md', '.prizmkit\specs\{{FEATURE_SLUG}}\plan.md') | ForEach-Object {
+  if (Test-Path $_) { $_ }
+}
 ```
 
 - spec.md missing: Run `/prizmkit-plan` → generate spec.md. Resolve any `[NEEDS CLARIFICATION]` markers using the task description — do NOT pause for interactive input.
 - plan.md missing: Run `/prizmkit-plan` → generate plan.md (change approach, components, interface design, data model, testing strategy, risk assessment, and Tasks section with `[ ]` checkboxes)
 
-> All files go under `.prizmkit/specs/{{FEATURE_SLUG}}/`. Confirm each with `ls` after writing.
+> All files go under `.prizmkit/specs/{{FEATURE_SLUG}}/`. Confirm each with `Test-Path` after writing.
 
 **Database Design Gate** (if feature involves data persistence — new tables, schema changes, new entities):
 Before proceeding past CP-1, verify:

package/bundled/dev-pipeline-windows/templates/sections/phase0-test-baseline.md

@@ -5,13 +5,11 @@
 **Step 2 — Record pre-existing failure baseline**:
 ```powershell
 # Run each test command, capture output
-& {
-  {{TEST_CMD}}
-} 2>&1 | Tee-Object (Join-Path $env:TEMP "test-baseline.txt") | Select-Object -Last 20
+& { {{TEST_CMD}} } 2>&1 | Tee-Object (Join-Path $env:TEMP "test-baseline.txt") | Select-Object -Last 20
 ```
 Save the list of **pre-existing failing tests** (if any) as `BASELINE_FAILURES`. These are known failures that existed before this session — Dev must NOT be blamed for them, but must list them in COMPLETION_SIGNAL.
 
-> **Test Output Rule**: Always capture test output to a temp file (`tee $env:TEMP\test-out.txt`). Then Select-String the file instead of re-running the suite.
+> **Test Output Rule**: Always capture test output to a temp file (`Tee-Object (Join-Path $env:TEMP "test-out.txt")`). Then use Select-String on the file instead of re-running the suite.
 
 
 **Checkpoint update**: Run the update script to set step `test-baseline` to `"completed"`:

package/bundled/dev-pipeline-windows/templates/sections/subagent-timeout-recovery.md

@@ -1,6 +1,6 @@
 ## Subagent Timeout Recovery
 
 If any agent times out:
-1. `ls .prizmkit/specs/{{FEATURE_SLUG}}/` — check what exists
+1. `Get-ChildItem -LiteralPath ".prizmkit/specs/{{FEATURE_SLUG}}/" -ErrorAction SilentlyContinue` — check what exists
 2. If `context-snapshot.md` exists: open recovery prompt with `"Read .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md for project context and any Implementation Log/Review Notes from previous agents. Run git diff HEAD to see actual code changes already made. Do NOT re-read individual source files unless the File Manifest directs you to."` + only remaining steps + `model: "lite"`
 3. Max 2 retries per phase. After 2 failures, orchestrator completes the work directly and appends a Recovery Note to context-snapshot.md.

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.70",
+  "version": "1.1.74",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.1.70",
+  "version": "1.1.74",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {