prizmkit 1.1.57 → 1.1.60

package/bundled/dev-pipeline-windows/templates/sections/checkpoint-system.md

@@ -0,0 +1,91 @@
+## Workflow Checkpoint System
+
+A checkpoint file tracks your progress through this workflow:
+
+**Path**: `{{CHECKPOINT_PATH}}`
+
+### Rules
+
+1. **Before each skill**: Read `workflow-checkpoint.json`, verify the previous step has `status: "completed"` or `status: "skipped"`. If it is still `"pending"` or `"in_progress"`, you MUST complete it first before moving on.
+
+2. **Starting a skill**: Use the update script to set the current step to `status: "in_progress"`.
+
+3. **After each skill completes**: Use the update script to set the current step to `status: "completed"`.
+
+4. **On failure**: Use the update script to set the step to `status: "failed"` and continue to the next step if possible, or halt and write failure-log.md.
+
+5. **On session exit**: The checkpoint file reflects your actual progress. Do NOT manually set future steps to "completed".
+
+### Checkpoint Update Pattern
+
+**IMPORTANT: NEVER hand-write or edit `workflow-checkpoint.json` directly. Always use the update script.**
+
+Define this helper once in the active PowerShell session before running PrizmKit Python scripts:
+
+```powershell
+function Invoke-PrizmPython {
+  param([Parameter(ValueFromRemainingArguments = $true)][string[]]$Arguments)
+  $python = Get-Command python -ErrorAction SilentlyContinue
+  if ($python) {
+    & $python.Source -c 'import sys; raise SystemExit(0 if sys.version_info[0] == 3 else 1)' *> $null
+    if ($LASTEXITCODE -eq 0) {
+      & $python.Source @Arguments
+      return
+    }
+  }
+  $py = Get-Command py -ErrorAction SilentlyContinue
+  if ($py) {
+    & $py.Source -3 -c 'import sys; raise SystemExit(0 if sys.version_info[0] == 3 else 1)' *> $null
+    if ($LASTEXITCODE -eq 0) {
+      & $py.Source -3 @Arguments
+      return
+    }
+  }
+  throw "Python 3 is required. Install Python and ensure python or py is in PATH."
+}
+```
+
+After completing each skill, run:
+
+```powershell
+Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
+  --checkpoint-path {{CHECKPOINT_PATH}} `
+  --step <SKILL_NAME> `
+  --status completed
+```
+
+For example, after completing `prizmkit-implement`:
+```powershell
+Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
+  --checkpoint-path {{CHECKPOINT_PATH}} `
+  --step prizmkit-implement `
+  --status completed
+```
+
+Before starting the next skill:
+```powershell
+Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
+  --checkpoint-path {{CHECKPOINT_PATH}} `
+  --step <NEXT_SKILL_NAME> `
+  --status in_progress
+```
+
+On failure:
+```powershell
+Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
+  --checkpoint-path {{CHECKPOINT_PATH}} `
+  --step <SKILL_NAME> `
+  --status failed `
+  --note "brief failure reason"
+```
+
+The script outputs JSON: `{"ok": true, ...}` on success, `{"ok": false, "error": "..."}` on failure.
+
+### Resume Behavior
+
+**Checkpoint is the primary source of truth for resume.** On retry sessions:
+
+1. Read `workflow-checkpoint.json` — steps already `"completed"` or `"skipped"` are skipped
+2. Start from the first `"pending"` or `"in_progress"` step
+3. If `failure-log.md` exists, read it for diagnostic context (the previous session failure reason, what approach to try differently) — but do NOT use it to determine the step to resume from
+4. If `workflow-checkpoint.json` is missing or corrupted, fall back to `failure-log.md` + the resume phase as the legacy mechanism

package/bundled/dev-pipeline-windows/templates/sections/context-budget-rules.md

@@ -0,0 +1,33 @@
+## Context Budget Rules (CRITICAL — read before any phase)
+
+You are running in **headless non-interactive mode** with a FINITE context window. Exceeding it will crash the session and lose all work. Follow these rules strictly:
+
+0. **NON-INTERACTIVE MODE** — There is NO human on the other end. NEVER ask for user confirmation, NEVER wait for user input, NEVER use interactive prompts (e.g. "Would you like me to…"). If a skill has an interactive step (e.g. offer remediation, ask for approval), skip it and proceed autonomously. Make decisions based on the data available and move forward.
+
+1. **context-snapshot.md is your single source of truth** — After it is built, ALWAYS read context-snapshot.md instead of re-reading individual source files
+2. **Never re-read your own writes** — After you create/modify a file, do NOT read it back to verify. Trust your write was correct.
+3. **Stay focused** — Do NOT explore code unrelated to this feature. No curiosity-driven reads.
+4. **One task at a time** — Complete and test one task before starting the next.
+5. **Minimize tool output** — Never load full command output into context. First capture to a temp file (`cmd 2>&1 | Tee-Object (Join-Path $env:TEMP "out.txt") | Select-Object -Last 20`), then scan the head/tail to identify relevant fields, and use targeted filtering (`Select-String`, `filtering`, `PowerShell object filtering`) to extract only the information needed for the current task. Only read the filtered result — never the raw full output.
+6. **No intermediate commits** — Do NOT run `git add`/`git commit` during implementation phases. All changes are committed once at the end via `/prizmkit-committer`.
+7. **Capture test output once** — When running test suites, always use `& { {{TEST_CMD}} } 2>&1 | Tee-Object (Join-Path $env:TEMP "test-out.txt") | Select-Object -Last 20`. Then Select-String (Join-Path $env:TEMP "test-out.txt") for details. Never re-run the suite just to apply a different filter.
+8. **Scaffold / generated file awareness (CRITICAL)** — When you run a scaffolding tool or package manager init command (`npm init`, `npx create-*`, `vite create`, `cargo init`, `go mod init`, `rails new`, `django-admin startproject`, `npx shadcn-ui init`, etc.), the output files are **generated boilerplate**. You MUST:
+   - Identify and mentally tag all files created by the tool as "scaffold files"
+   - Record the list of scaffold-generated files in context-snapshot.md under a `### Scaffold Files (do not re-read)` section
+   - **NEVER re-read scaffold files** after initial creation. Their content is standard boilerplate — you already know what they contain from the tool that generated them
+   - If you need to modify a scaffold file, make the edit directly without reading it first (you know the standard template content)
+   - This applies equally to `node_modules/`, `package-lock.json`, generated config files (`tsconfig.json`, `vite.config.ts`, `tailwind.config.js`, `.eslintrc`, etc.) produced by init commands
+   - When passing context to subagents, explicitly tell them the scaffold-generated files so they skip reading them too
+9. **Package version verification (HARD CONSTRAINT — BLOCKING)** — Before writing ANY dependency version in `package.json`, `requirements.txt`, `Cargo.toml`, `go.mod`, `Gemfile`, `pyproject.toml`, or any other dependency manifest:
+   - You MUST verify the real version exists by querying the package registry first:
+     - npm/Node.js: `npm view <package> dist-tags.latest 2>$null`
+     - Python/pip: `pip index versions <package> 2>$null | Select-Object -First 1`
+     - Go: `go list -m -versions <module>@latest 2>$null`
+     - Rust: `cargo search <crate> --limit 1 2>$null`
+   - **NEVER guess or hallucinate version numbers**. If you cannot verify a version, use `"latest"` or `"*"` as a placeholder, or omit the version constraint entirely and let the package manager resolve it
+   - If the registry query fails (network issue, package not found), you MUST either:
+     (a) Use a known-safe version you have high confidence in, OR
+     (b) Skip that dependency and document it as a manual step, OR
+     (c) Use no version constraint (e.g., `"express": "*"`)
+   - **This is a BLOCKING gate**: do NOT run `npm install` / `pip install` / `cargo build` / `go mod tidy` until ALL versions in the manifest have been verified or use open constraints
+   - Batch version lookups: query multiple packages in parallel to save time (e.g., run multiple `npm view` commands concurrently)

package/bundled/dev-pipeline-windows/templates/sections/critical-paths-agent.md

@@ -0,0 +1,10 @@
+## Critical Paths
+
+| Resource | Path |
+|----------|------|
+| Feature Artifacts Dir | `.prizmkit/specs/{{FEATURE_SLUG}}/` |
+| Context Snapshot | `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` |
+| Dev Agent Def | {{DEV_SUBAGENT_PATH}} |
+| Reviewer Agent Def | {{REVIEWER_SUBAGENT_PATH}} |
+| Critic Agent Def (if enabled) | {{CRITIC_SUBAGENT_PATH}} |
+| Project Root | {{PROJECT_ROOT}} |

package/bundled/dev-pipeline-windows/templates/sections/critical-paths-full.md

@@ -0,0 +1,12 @@
+## Critical Paths
+
+| Resource | Path |
+|----------|------|
+| Feature Artifacts Dir | `.prizmkit/specs/{{FEATURE_SLUG}}/` |
+| Context Snapshot | `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` |
+| Team Config | `{{TEAM_CONFIG_PATH}}` |
+| Dev Agent Def | {{DEV_SUBAGENT_PATH}} |
+| Reviewer Agent Def | {{REVIEWER_SUBAGENT_PATH}} |
+| Critic Agent Def | {{CRITIC_SUBAGENT_PATH}} |
+| Project Root | {{PROJECT_ROOT}} |
+| Feature List Path | {{FEATURE_LIST_PATH}} |

package/bundled/dev-pipeline-windows/templates/sections/critical-paths-lite.md

@@ -0,0 +1,7 @@
+## Critical Paths
+
+| Resource | Path |
+|----------|------|
+| Feature Artifacts Dir | `.prizmkit/specs/{{FEATURE_SLUG}}/` |
+| Context Snapshot | `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` |
+| Project Root | {{PROJECT_ROOT}} |

package/bundled/dev-pipeline-windows/templates/sections/directory-convention-agent.md

@@ -0,0 +1,8 @@
+## PrizmKit Directory Convention
+
+```
+.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md  ← orchestrator writes Sections 1-4; Dev appends Implementation Log; Reviewer appends Review Notes
+.prizmkit/specs/{{FEATURE_SLUG}}/plan.md              ← includes Tasks section
+```
+
+**`context-snapshot.md`** is the shared knowledge base. Orchestrator writes Sections 1-4; Dev appends Implementation Log; Reviewer appends Review Notes. Append-only after initial creation.

package/bundled/dev-pipeline-windows/templates/sections/directory-convention-full.md

@@ -0,0 +1,9 @@
+## PrizmKit Directory Convention
+
+```
+.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md  ← orchestrator writes Sections 1-4; Dev appends Implementation Log; Reviewer appends Review Notes
+.prizmkit/specs/{{FEATURE_SLUG}}/spec.md
+.prizmkit/specs/{{FEATURE_SLUG}}/plan.md              ← includes Tasks section
+```
+
+**`context-snapshot.md`** is the shared knowledge base. Orchestrator writes Sections 1-4; Dev appends Implementation Log; Reviewer appends Review Notes. This eliminates redundant I/O across all agents.

package/bundled/dev-pipeline-windows/templates/sections/directory-convention-lite.md

@@ -0,0 +1,6 @@
+## PrizmKit Directory Convention
+
+```
+.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md
+.prizmkit/specs/{{FEATURE_SLUG}}/plan.md              ← includes Tasks section
+```

package/bundled/dev-pipeline-windows/templates/sections/failure-capture.md

@@ -0,0 +1,21 @@
+## Failure Capture Protocol
+
+If you encounter an unrecoverable error, context overflow, or are about to exit without completing all phases:
+
+1. Write `.prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md` BEFORE exiting:
+   ```
+   FAILURE_TYPE: timeout | test_failure | review_rejected | context_overflow | unknown
+   PHASE: <failed phase>
+   ROOT_CAUSE: <1-2 sentence explanation>
+   ATTEMPTED: <approaches already tried>
+   SUGGESTION: <what the next session should try differently>
+   DISCOVERED_TRAPS:
+   - [CRITICAL|HIGH|LOW] <gotcha discovered during this failed session> | FIX: <approach>
+   ```
+
+2. This file is intentionally lightweight — write it BEFORE context runs out.
+
+**Lifecycle**: failure-log.md is a temporary cross-session artifact. Do NOT commit it to git. After a successful session (all phases complete + commit done), delete it:
+```powershell
+Remove-Item -Force -ErrorAction SilentlyContinue .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md
+```

package/bundled/dev-pipeline-windows/templates/sections/feature-context.md

@@ -0,0 +1,31 @@
+<feature-context>
+### Feature Description
+
+{{FEATURE_DESCRIPTION}}
+
+{{USER_CONTEXT}}
+
+### Acceptance Criteria
+
+{{ACCEPTANCE_CRITERIA}}
+
+### Project Brief
+
+> Product ideas checklist from planning. Lines marked [x] are already implemented. When your feature touches any [ ] item, ensure alignment. After implementation, mark relevant items [x] and append the key file/directory paths.
+
+{{PROJECT_BRIEF}}
+
+### Dependencies (Already Completed)
+
+> Below are features that this feature depends on, along with their key implementation notes. Use this context to understand what has already been built and what interfaces/APIs/models are available.
+
+{{COMPLETED_DEPENDENCIES}}
+
+### App Global Context
+
+{{GLOBAL_CONTEXT}}
+
+### Project Conventions
+
+> Read {{PLATFORM_CONVENTIONS}} for project-level coding standards, architecture decisions, and development rules. Follow these conventions throughout implementation.
+</feature-context>

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

@@ -0,0 +1,72 @@
+### Browser Verification — MANDATORY
+
+You MUST execute this phase. Use native PowerShell commands for setup, server lifecycle, and cleanup.
+
+**Tool readiness**:
+```powershell
+$playwright = Get-Command playwright-cli -ErrorAction SilentlyContinue
+$opencli = Get-Command opencli -ErrorAction SilentlyContinue
+if ($playwright) { playwright-cli --version } else { "PLAYWRIGHT_CLI:NOT_INSTALLED" }
+if ($opencli) { opencli --version } else { "OPENCLI:NOT_INSTALLED" }
+```
+
+If neither browser tool is available, install playwright-cli as the default:
+```powershell
+npm install -g @playwright/cli@latest
+playwright-cli --version
+```
+
+**Choose the tool**:
+- Use `playwright-cli` for isolated local dev-server verification.
+- Use `opencli` when the scenario needs an existing Chrome login/session.
+- If opencli is selected, verify connectivity with `opencli doctor` before browser actions.
+
+**Dev server setup**:
+```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" }
+
+# Replace <start-command> with the project-specific dev command.
+$server = Start-Process -FilePath "powershell" -ArgumentList @("-NoProfile", "-Command", "<start-command>") -PassThru
+$DEV_SERVER_PID = $server.Id
+```
+
+Wait for readiness:
+```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" }
+```
+
+**Verification goals**:
+{{BROWSER_VERIFY_STEPS}}
+
+Use the selected browser tool to inspect current page state, perform actions, and take a final screenshot:
+- `playwright-cli open http://localhost:$DEV_PORT`, `playwright-cli snapshot`, `playwright-cli screenshot`, `playwright-cli close`
+- `opencli browser open http://localhost:$DEV_PORT`, `opencli browser state`, `opencli browser screenshot`, `opencli browser close`
+
+**Cleanup**:
+```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 }
+```
+
+Append results to `context-snapshot.md` with tool, URL, commands used, screenshot path, PASS/FAIL reason, and cleanup status.
+
+**Checkpoint update**:
+```powershell
+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-browser-verification-opencli.md

@@ -0,0 +1,63 @@
+### Browser Verification (opencli) — MANDATORY
+
+You MUST execute this phase with `opencli browser`. Use native PowerShell commands for setup, server lifecycle, and cleanup.
+
+**Readiness**:
+```powershell
+$opencli = Get-Command opencli -ErrorAction SilentlyContinue
+if ($opencli) { opencli --version } else { "OPENCLI:NOT_INSTALLED" }
+opencli doctor
+```
+
+If opencli is not available, install it:
+```powershell
+npm install -g @jackwener/opencli@latest
+opencli --version
+```
+
+**Dev server setup**:
+```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
+```
+
+Wait for readiness:
+```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" }
+```
+
+**Verification goals**:
+{{BROWSER_VERIFY_STEPS}}
+
+Use `opencli browser open http://localhost:$DEV_PORT`, `opencli browser state`, indexed interaction commands from `opencli browser --help`, and `opencli browser screenshot`.
+
+**Cleanup**:
+```powershell
+opencli browser 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 }
+```
+
+Append results to `context-snapshot.md` with URL, command used, opencli version, steps executed, screenshot path, PASS/FAIL reason, and cleanup status.
+
+**Checkpoint update**:
+```powershell
+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-browser-verification.md

@@ -0,0 +1,62 @@
+### Browser Verification (playwright-cli) — MANDATORY
+
+You MUST execute this phase with `playwright-cli`. Use native PowerShell commands for setup, server lifecycle, and cleanup.
+
+**Readiness**:
+```powershell
+$playwright = Get-Command playwright-cli -ErrorAction SilentlyContinue
+if ($playwright) { playwright-cli --version } else { "PLAYWRIGHT_CLI:NOT_INSTALLED" }
+```
+
+If playwright-cli is not available, install it:
+```powershell
+npm install -g @playwright/cli@latest
+playwright-cli --version
+```
+
+**Dev server setup**:
+```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
+```
+
+Wait for readiness:
+```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" }
+```
+
+**Verification 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`.
+
+**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 }
+```
+
+Append results to `context-snapshot.md` with URL, command used, playwright-cli version, steps executed, screenshot path, PASS/FAIL reason, and cleanup status.
+
+**Checkpoint update**:
+```powershell
+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

@@ -0,0 +1,71 @@
+### Architecture Sync & Commit (SINGLE COMMIT) — DO NOT SKIP
+
+**a.** Check if feature already committed:
+```powershell
+git log --oneline | Select-String "{{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.
+
+**b.** Run `/prizmkit-retrospective` (**before commit**, maintains `.prizmkit/prizm-docs/` architecture index):
+1. **Structural sync**: update KEY_FILES/INTERFACES/DEPENDENCIES/file counts for changed modules
+2. **Architecture knowledge**: extract TRAPS, RULES, DECISIONS from completed work into `.prizmkit/prizm-docs/`
+3. **L2 coverage check**: For any module/sub-module with source files created or significantly modified in this session but no L2 `.prizm` doc — evaluate whether L2 is warranted and create if so. The current session has the best context for accurate KEY_FILES, TRAPS, and DECISIONS.
+4. Stage doc changes: `git add .prizmkit/prizm-docs/`
+⚠️ Do NOT commit here. Only stage.
+
+**c.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
+```powershell
+git add <specific-files-created-or-modified>
+git add .prizmkit/prizm-docs/
+```
+
+**d.** Run `/prizmkit-committer` → THE ONLY commit for this feature:
+`feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
+This single commit includes: feature code + tests + .prizmkit/prizm-docs/ updates. Do NOT push.
+- MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
+- Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
+
+**e.** Final verification:
+```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.
+
+**f.** Write completion summary for downstream dependency context:
+
+Write `.prizmkit/specs/{{FEATURE_SLUG}}/completion-summary.json` with the key changes from this session. This file is NOT committed to git — the pipeline runner reads it to propagate context to dependent features.
+
+```json
+{
+  "completion_notes": [
+    "<each item: one key change, API, model, or integration point that downstream features may need>",
+    "Example: Added User model (id, email, password_hash, display_name) in prisma/schema.prisma",
+    "Example: POST /api/auth/register and POST /api/auth/login endpoints in src/api/auth.ts",
+    "Example: Auth middleware in src/middleware/auth.ts — validates JWT on protected routes"
+  ]
+}
+```
+
+Rules for writing completion notes:
+- Focus on **what downstream features need to know**: new APIs, models, exported functions, key file paths
+- Each note should be self-contained and concise (one line, under 120 characters preferred)
+- Include 3-8 notes covering the most important changes
+- Do NOT include test files, config changes, or internal implementation details unless they affect other features
+- If this feature has no downstream dependents, still write the summary (it serves as documentation)
+
+
+**Checkpoint update**: After `/prizmkit-retrospective` completes, run the update script to set step `prizmkit-retrospective` to `"completed"`:
+```powershell
+Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
+  --checkpoint-path {{CHECKPOINT_PATH}} `
+  --step prizmkit-retrospective `
+  --status completed
+```
+After `/prizmkit-committer` completes, set step `prizmkit-committer` to `"completed"`:
+```powershell
+Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
+  --checkpoint-path {{CHECKPOINT_PATH}} `
+  --step prizmkit-committer `
+  --status completed
+```

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

@@ -0,0 +1,64 @@
+### Architecture Sync & Commit (SINGLE COMMIT)
+
+**a.** Run `/prizmkit-retrospective` — maintains `.prizmkit/prizm-docs/` (architecture index):
+1. **Structural sync**: Use `git diff --cached --name-status` to locate changed modules, update KEY_FILES/INTERFACES/DEPENDENCIES/file counts in affected `.prizmkit/prizm-docs/` files
+2. **Architecture knowledge** (feature sessions only): Extract TRAPS/RULES/DECISIONS from completed work into `.prizmkit/prizm-docs/`
+3. **L2 coverage check**: For any module/sub-module with source files created or significantly modified in this session but no L2 `.prizm` doc — evaluate whether L2 is warranted and create if so. The current session has the best context for accurate KEY_FILES, TRAPS, and DECISIONS.
+4. Stage doc changes: `git add .prizmkit/prizm-docs/`
+⚠️ Do NOT commit here. Only stage.
+
+**b.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
+```powershell
+git add <specific-files-created-or-modified>
+git add .prizmkit/prizm-docs/
+```
+
+**c.** Run `/prizmkit-committer` → THE ONLY commit for this feature:
+`feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
+This single commit includes: feature code + tests + .prizmkit/prizm-docs/ updates. Do NOT push.
+- MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
+- Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
+
+**d.** Final verification:
+```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.
+
+**e.** Write completion summary for downstream dependency context:
+
+Write `.prizmkit/specs/{{FEATURE_SLUG}}/completion-summary.json` with the key changes from this session. This file is NOT committed to git — the pipeline runner reads it to propagate context to dependent features.
+
+```json
+{
+  "completion_notes": [
+    "<each item: one key change, API, model, or integration point that downstream features may need>",
+    "Example: Added User model (id, email, password_hash, display_name) in prisma/schema.prisma",
+    "Example: POST /api/auth/register and POST /api/auth/login endpoints in src/api/auth.ts",
+    "Example: Auth middleware in src/middleware/auth.ts — validates JWT on protected routes"
+  ]
+}
+```
+
+Rules for writing completion notes:
+- Focus on **what downstream features need to know**: new APIs, models, exported functions, key file paths
+- Each note should be self-contained and concise (one line, under 120 characters preferred)
+- Include 3-8 notes covering the most important changes
+- Do NOT include test files, config changes, or internal implementation details unless they affect other features
+- If this feature has no downstream dependents, still write the summary (it serves as documentation)
+
+
+**Checkpoint update**: After `/prizmkit-retrospective` completes, run the update script to set step `prizmkit-retrospective` to `"completed"`:
+```powershell
+Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
+  --checkpoint-path {{CHECKPOINT_PATH}} `
+  --step prizmkit-retrospective `
+  --status completed
+```
+After `/prizmkit-committer` completes, set step `prizmkit-committer` to `"completed"`:
+```powershell
+Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
+  --checkpoint-path {{CHECKPOINT_PATH}} `
+  --step prizmkit-committer `
+  --status completed
+```

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

@@ -0,0 +1,23 @@
+   - **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:
+     ### Files to Modify
+     | File | Why Needed | Key Interfaces |
+     |------|-----------|----------------|
+     | `<source-dir>/config.js` | Add runtime config layer | `config` (Zod object), `configSchema` |
+
+     ### Files for Reference
+     | File | Why Needed | Key Interfaces |
+     |------|-----------|----------------|
+     | `<source-dir>/security/permission-guard.js` | Permission check integration | `checkCommandPermission(userId, cmd)` |
+
+     ### Known TRAPS (from .prizmkit/prizm-docs/)
+     - <trap entries extracted from L1/L2 docs>
+
+
+**Checkpoint update**: Run the update script to set step `context-snapshot` to `"completed"`:
+```powershell
+Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
+  --checkpoint-path {{CHECKPOINT_PATH}} `
+  --step context-snapshot `
+  --status completed
+```

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

@@ -0,0 +1,24 @@
+### Build Context Snapshot
+
+```powershell
+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 — Feature Brief**: feature description + acceptance criteria (copy from 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
+     ```

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

@@ -0,0 +1,12 @@
+   - **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
+
+
+**Checkpoint update**: Run the update script to set step `context-snapshot` to `"completed"`:
+```powershell
+Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
+  --checkpoint-path {{CHECKPOINT_PATH}} `
+  --step context-snapshot `
+  --status completed
+```