prizmkit 1.0.152 → 1.1.0

package/bundled/dev-pipeline/scripts/parse-stream-progress.py

@@ -28,7 +28,7 @@ from datetime import datetime, timezone
 # Ordered pipeline phases — index defines forward-only progression.
 # Phase detection is monotonic: once a phase is reached, earlier phases
 # cannot be re-entered (prevents false positives from file content mentions).
-PHASE_ORDER = ["specify", "plan", "analyze", "implement", "code-review", "retrospective", "commit"]
+PHASE_ORDER = ["plan", "analyze", "implement", "code-review", "retrospective", "commit"]
 
 # Keywords for phase detection.
 # "strong" keywords are skill invocations — high confidence, but still
@@ -36,13 +36,9 @@ PHASE_ORDER = ["specify", "plan", "analyze", "implement", "code-review", "retros
 # "weak" keywords are contextual hints — also forward-only, used when no
 # strong keyword matches.
 PHASE_KEYWORDS = {
-    "specify": {
-        "strong": ["prizmkit-specify"],
-        "weak": ["spec.md", "specification", "gathering requirements"],
-    },
     "plan": {
         "strong": ["prizmkit-plan"],
-        "weak": ["plan.md", "architecture", "task checklist", "task breakdown"],
+        "weak": ["spec.md", "plan.md", "specification", "architecture", "task checklist", "task breakdown", "gathering requirements"],
     },
     "analyze": {
         "strong": ["prizmkit-analyze"],

package/bundled/dev-pipeline/templates/bootstrap-tier1.md

@@ -23,6 +23,12 @@ You are the **session orchestrator**. Implement Feature {{FEATURE_ID}}: "{{FEATU
 
 {{ACCEPTANCE_CRITERIA}}
 
+### Project Brief
+
+> Distilled summary of the project's key requirements and design decisions, captured during planning. When your feature implementation touches any of these key points, ensure alignment.
+
+{{PROJECT_BRIEF}}
+
 ### Dependencies (Already Completed)
 
 {{COMPLETED_DEPENDENCIES}}
@@ -41,7 +47,7 @@ You are running in headless mode with a FINITE context window. Exceeding it will
 4. **One task at a time** — In Phase 3 (implement), complete and test one task before starting the next.
 5. **Minimize tool output** — When running commands, use `| head -20` or `| tail -20` to limit output. Never dump entire test suites or logs.
 6. **No intermediate commits** — Do NOT run `git add`/`git commit` during Phase 1-3. All changes are committed once at the end in Phase 4 via `/prizmkit-committer`.
-7. **Capture test output once** — When running the test suite, always use `$TEST_CMD 2>&1 | tee /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
+7. **Capture test output once** — When running test suites, always use `$TEST_CMD 2>&1 | tee /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
 
 ---
 
@@ -130,14 +136,11 @@ grep -q '^/binary-name$' .gitignore || echo '/binary-name' >> .gitignore
 ```
 Never commit compiled binaries, build output, or generated artifacts.
 
-**3a.** Detect the test command and record baseline:
-```bash
-# Try in order, use first that exits 0
-node --test tests/**/*.test.js 2>&1 | tail -3   # Node built-in
-npm test 2>&1 | tail -3                          # npm fallback
-```
-Record the working command as `TEST_CMD`. Then record baseline failures (if any):
+**3a.** Detect test commands and record baseline:
+
+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` (one or more commands). Then record baseline:
 ```bash
+# Run each test command, capture output
 $TEST_CMD 2>&1 | tee /tmp/test-baseline.txt | tail -20
 ```
 
@@ -191,6 +194,43 @@ You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without
 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.
 {{END_IF_BROWSER_INTERACTION}}
 
+### Phase 3.8: Local Deploy Verification
+
+You just implemented this feature — you know the project's tech stack and build tools.
+
+1. **Build**: Run the project's build/compile commands. If a required tool is missing, install it first.
+2. **Fix**: If build fails with code errors (type errors, missing imports, config issues), fix them (max 2 rounds), then re-verify.
+3. **Assess and record** — append to context-snapshot.md:
+   - **ALL builds pass** → `## Deploy Verification: PASS` — proceed to commit
+   - **Some builds fail with fixable errors** → fix and re-verify (already handled in step 2)
+   - **Cannot build locally** (missing system-level deps you cannot install) → Generate `DEPLOY.md` with:
+     ```
+     # Local Development Setup
+
+     ## Prerequisites
+     - [tool]: [install instruction]
+
+     ## Build Steps
+     1. [exact command]
+
+     ## Run / Dev Mode
+     [exact command to start the app locally]
+
+     ## Verify
+     [how to confirm the app is running correctly]
+     ```
+     Record: `## Deploy Verification: PARTIAL — see DEPLOY.md for missing prerequisites`
+
+Deploy verification does NOT block the commit, but you MUST attempt it.
+
+**Step 4 — Smoke test** (only if build passed and project can be started):
+1. Start the project locally (e.g., `make dev`, `npm start`, `go run .`, etc.)
+2. Verify basic functionality: hit key endpoints, check health routes, confirm the UI loads
+3. Stop the server process you started — do NOT leave it running
+4. Record smoke test results in `## Deploy Verification` section
+
+If the project cannot be started locally (e.g., requires external services, databases, credentials), skip the smoke test and note why.
+
 ### Phase 4: Architecture Sync & Commit (SINGLE COMMIT)
 
 **4a.** Run `/prizmkit-retrospective` — maintains `.prizm-docs/` (architecture index):

package/bundled/dev-pipeline/templates/bootstrap-tier2.md

@@ -23,6 +23,12 @@ You are the **session orchestrator**. Implement Feature {{FEATURE_ID}}: "{{FEATU
 
 {{ACCEPTANCE_CRITERIA}}
 
+### Project Brief
+
+> Distilled summary of the project's key requirements and design decisions, captured during planning. When your feature implementation touches any of these key points, ensure alignment.
+
+{{PROJECT_BRIEF}}
+
 ### Dependencies (Already Completed)
 
 {{COMPLETED_DEPENDENCIES}}
@@ -41,7 +47,7 @@ You are running in headless mode with a FINITE context window. Exceeding it will
 4. **One task at a time** — In Phase 4 (implement), complete and test one task before starting the next.
 5. **Minimize tool output** — When running commands, use `| head -20` or `| tail -20` to limit output. Never dump entire test suites or logs.
 6. **No intermediate commits** — Do NOT run `git add`/`git commit` during Phase 1-5. All changes are committed once at the end in Phase 6 via `/prizmkit-committer`.
-7. **Capture test output once** — When running the test suite, always use `$TEST_CMD 2>&1 | tee /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
+7. **Capture test output once** — When running test suites, always use `$TEST_CMD 2>&1 | tee /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
 
 ---
 
@@ -82,6 +88,16 @@ If any agent times out:
 Check `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` — if exists, skip Phase 1 and proceed to Phase {{RESUME_PHASE}}.
 {{END_IF_RESUME}}
 
+### Phase 0.5: Detect Test Commands
+
+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:
+```bash
+$TEST_CMD 2>&1 | tee /tmp/test-baseline.txt | tail -20
+```
+Save pre-existing failing tests as `BASELINE_FAILURES`.
+
+> **⚠️ Test Output Rule**: Always capture test output to a temp file (`tee /tmp/test-out.txt`). Then grep the file instead of re-running the suite.
+
 ### Phase 1: Build Context Snapshot (you, the orchestrator)
 
 **Check for previous failure log:**
@@ -302,6 +318,43 @@ You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without
 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.
 {{END_IF_BROWSER_INTERACTION}}
 
+### Phase 5.8: Local Deploy Verification
+
+You just implemented this feature — you know the project's tech stack and build tools.
+
+1. **Build**: Run the project's build/compile commands. If a required tool is missing, install it first.
+2. **Fix**: If build fails with code errors (type errors, missing imports, config issues), fix them (max 2 rounds), then re-verify.
+3. **Assess and record** — append to context-snapshot.md:
+   - **ALL builds pass** → `## Deploy Verification: PASS` — proceed to commit
+   - **Some builds fail with fixable errors** → fix and re-verify (already handled in step 2)
+   - **Cannot build locally** (missing system-level deps you cannot install) → Generate `DEPLOY.md` with:
+     ```
+     # Local Development Setup
+
+     ## Prerequisites
+     - [tool]: [install instruction]
+
+     ## Build Steps
+     1. [exact command]
+
+     ## Run / Dev Mode
+     [exact command to start the app locally]
+
+     ## Verify
+     [how to confirm the app is running correctly]
+     ```
+     Record: `## Deploy Verification: PARTIAL — see DEPLOY.md for missing prerequisites`
+
+Deploy verification does NOT block the commit, but you MUST attempt it.
+
+**Step 4 — Smoke test** (only if build passed and project can be started):
+1. Start the project locally (e.g., `make dev`, `npm start`, `go run .`, etc.)
+2. Verify basic functionality: hit key endpoints, check health routes, confirm the UI loads
+3. Stop the server process you started — do NOT leave it running
+4. Record smoke test results in `## Deploy Verification` section
+
+If the project cannot be started locally (e.g., requires external services, databases, credentials), skip the smoke test and note why.
+
 ### Phase 6: Architecture Sync & Commit (SINGLE COMMIT)
 
 **6a.** Run `/prizmkit-retrospective` — maintains `.prizm-docs/` (architecture index):

package/bundled/dev-pipeline/templates/bootstrap-tier3.md

@@ -23,6 +23,12 @@ You are the **session orchestrator**. Implement Feature {{FEATURE_ID}}: "{{FEATU
 
 {{ACCEPTANCE_CRITERIA}}
 
+### Project Brief
+
+> Distilled summary of the project's key requirements and design decisions, captured during planning. When your feature implementation touches any of these key points, ensure alignment.
+
+{{PROJECT_BRIEF}}
+
 ### Dependencies (Already Completed)
 
 {{COMPLETED_DEPENDENCIES}}
@@ -75,23 +81,18 @@ If any agent times out:
 - **CP-0**: Verify `.prizm-docs/root.prizm`, `.prizmkit/config.json` exist
 {{END_IF_INIT_NEEDED}}
 {{IF_INIT_DONE}}
-### Phase 0: Record Test Baseline & Detect Test Command
+### Phase 0: Record Test Baseline & Detect Test Commands
 
-**Step 1 — Detect the correct test command** (run once, save as `TEST_CMD`):
-```bash
-# Try in order, use the first one that exits 0
-node --test tests/**/*.test.js 2>&1 | tail -3   # Node built-in
-npm test 2>&1 | tail -3                          # npm script fallback
-```
-Record the working command as `TEST_CMD`. If both fail, record `TEST_CMD="npm test"` as default.
+**Step 1 — Detect test commands**: 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`.
 
 **Step 2 — Record pre-existing failure baseline**:
 ```bash
+# Run each test command, capture output
 $TEST_CMD 2>&1 | tee /tmp/test-baseline.txt | tail -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 /tmp/test-out.txt`). Then grep the file instead of re-running the suite. Never run `npm test` multiple times just to apply different grep filters to the output.
+> **⚠️ Test Output Rule**: Always capture test output to a temp file (`tee /tmp/test-out.txt`). Then grep the file instead of re-running the suite.
 {{END_IF_INIT_DONE}}
 
 ### Step 1: Initialize
@@ -182,7 +183,7 @@ If `EXISTING_CODE` is non-empty: your spec/plan/tasks must reflect this existing
 ls .prizmkit/specs/{{FEATURE_SLUG}}/spec.md .prizmkit/specs/{{FEATURE_SLUG}}/plan.md 2>/dev/null
 ```
 
-- spec.md missing: Run `/prizmkit-specify` → generate spec.md. Resolve any `[NEEDS CLARIFICATION]` markers using the feature description — do NOT pause for interactive input.
+- spec.md missing: Run `/prizmkit-plan` → generate spec.md. Resolve any `[NEEDS CLARIFICATION]` markers using the feature description — do NOT pause for interactive input.
 - plan.md missing: Run `/prizmkit-plan` → generate plan.md (architecture, 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.
@@ -400,6 +401,42 @@ You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without
 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.
 {{END_IF_BROWSER_INTERACTION}}
 
+### Phase 5.8: Local Deploy Verification
+
+You just implemented this feature — you know the project's tech stack and build tools.
+
+1. **Build**: Run the project's build/compile commands. If a required tool is missing, install it first.
+2. **Fix**: If build fails with code errors (type errors, missing imports, config issues), fix them (max 2 rounds), then re-verify.
+3. **Assess and record** — append to context-snapshot.md:
+   - **ALL builds pass** → `## Deploy Verification: PASS` — proceed to commit
+   - **Some builds fail with fixable errors** → fix and re-verify (already handled in step 2)
+   - **Cannot build locally** (missing system-level deps you cannot install) → Generate `DEPLOY.md` with:
+     ```
+     # Local Development Setup
+
+     ## Prerequisites
+     - [tool]: [install instruction]
+
+     ## Build Steps
+     1. [exact command]
+
+     ## Run / Dev Mode
+     [exact command to start the app locally]
+
+     ## Verify
+     [how to confirm the app is running correctly]
+     ```
+     Record: `## Deploy Verification: PARTIAL — see DEPLOY.md for missing prerequisites`
+
+Deploy verification does NOT block the commit, but you MUST attempt it.
+
+**Step 4 — Smoke test** (only if build passed and project can be started):
+1. Start the project locally (e.g., `make dev`, `npm start`, `go run .`, etc.)
+2. Verify basic functionality: hit key endpoints, check health routes, confirm the UI loads
+3. Stop the server process you started — do NOT leave it running
+4. Record smoke test results in `## Deploy Verification` section
+
+If the project cannot be started locally (e.g., requires external services, databases, credentials), skip the smoke test and note why.
 
 ### Phase 6: Retrospective & Commit (SINGLE COMMIT) — DO NOT SKIP
 

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

@@ -0,0 +1,11 @@
+## Context Budget Rules (CRITICAL — read before any phase)
+
+You are running in headless mode with a FINITE context window. Exceeding it will crash the session and lose all work. Follow these rules strictly:
+
+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** — When running commands, use `| head -20` or `| tail -20` to limit output. Never dump entire test suites or logs.
+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 /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.

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

@@ -0,0 +1,9 @@
+## 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}} |
+| Project Root | {{PROJECT_ROOT}} |

package/bundled/dev-pipeline/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/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/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/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/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/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: <which phase failed>
+   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:
+```bash
+rm -f .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md
+```

package/bundled/dev-pipeline/templates/sections/failure-log-check.md

@@ -0,0 +1,8 @@
+**Check for previous failure log:**
+```bash
+cat .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md 2>/dev/null || echo "NO_PREVIOUS_FAILURE"
+```
+If failure-log.md exists:
+- Read ROOT_CAUSE and SUGGESTION — adjust your approach accordingly
+- Read DISCOVERED_TRAPS — if any are genuine, inject into .prizm-docs/ during the commit phase retrospective
+- Do NOT delete failure-log.md until this session completes all phases and commits successfully

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

@@ -0,0 +1,23 @@
+<feature-context>
+### Feature Description
+
+{{FEATURE_DESCRIPTION}}
+
+### Acceptance Criteria
+
+{{ACCEPTANCE_CRITERIA}}
+
+### Project Brief
+
+> Distilled summary of the project's key requirements and design decisions, captured during planning. When your feature implementation touches any of these key points, ensure alignment.
+
+{{PROJECT_BRIEF}}
+
+### Dependencies (Already Completed)
+
+{{COMPLETED_DEPENDENCIES}}
+
+### App Global Context
+
+{{GLOBAL_CONTEXT}}
+</feature-context>

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

@@ -0,0 +1,15 @@
+### Analyze — Reviewer Subagent
+
+Spawn Reviewer agent (Agent tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false).
+
+Prompt:
+> "Read {{REVIEWER_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
+> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — Section 3 has project context, Section 4 has file manifest.
+> 2. Run prizmkit-analyze: cross-check `plan.md` (including Tasks section) against feature description and acceptance criteria for consistency.
+> 3. Before flagging CRITICAL or HIGH issues, read the relevant source files listed in the File Manifest to verify.
+> Report: CRITICAL, HIGH, MEDIUM issues found (or 'No issues found')."
+
+Wait for Reviewer to return.
+- If CRITICAL issues found: fix them yourself — read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` for full project context. Fix ONLY the listed CRITICAL issues in plan.md. Then re-run analyze (max 1 round).
+
+**CP-2**: No CRITICAL issues.

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

@@ -0,0 +1,15 @@
+### Analyze — Reviewer Agent
+
+Spawn Reviewer agent (Agent tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false).
+
+Prompt:
+> "Read {{REVIEWER_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
+> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — Section 3 has project context, Section 4 has file manifest.
+> 2. Run prizmkit-analyze: cross-check `spec.md` and `plan.md` (including Tasks section) for consistency.
+> 3. Before flagging CRITICAL or HIGH issues, read the relevant source files listed in the File Manifest to verify.
+> Report: CRITICAL, HIGH, MEDIUM issues found (or 'No issues found')."
+
+Wait for Reviewer to return.
+- If CRITICAL issues found: fix them yourself — read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` for full project context. Fix ONLY the listed CRITICAL issues in spec.md/plan.md. Then re-run analyze (max 1 round).
+
+**CP-2**: No CRITICAL issues.

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

@@ -0,0 +1,31 @@
+### Browser Verification (playwright-cli) — MANDATORY
+
+You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without actually running playwright-cli.
+
+**Startup**:
+1. Check if port is already in use: `lsof -ti:3001 | xargs kill -9 2>/dev/null || true`
+2. Start dev server: `{{BROWSER_SETUP_COMMAND}}`
+3. Wait for server to be ready: poll `{{BROWSER_URL}}` with `curl -s -o /dev/null -w "%{http_code}"` until it returns 200 or 302 (max 30 seconds, 2s interval)
+4. If the page requires authentication, use playwright-cli to register a test user and log in first
+
+**Verification**:
+5. Use `playwright-cli` to open `{{BROWSER_URL}}`, then verify:
+   {{BROWSER_VERIFY_STEPS}}
+6. Take a final screenshot for evidence
+
+**Cleanup (REQUIRED — you started it, you stop it)**:
+7. Stop the dev server process you started in step 2 (kill the process)
+8. Verify port is released: `lsof -ti:3001 | xargs kill -9 2>/dev/null || true`
+
+**Reporting**:
+9. Append results to `context-snapshot.md`:
+   ```
+   ## Browser Verification
+   URL: {{BROWSER_URL}}
+   Steps executed: [list]
+   Screenshot: [path]
+   Result: PASS / FAIL (reason)
+   Server cleanup: confirmed
+   ```
+
+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.

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

@@ -0,0 +1,36 @@
+### Architecture Sync & Commit (SINGLE COMMIT) — DO NOT SKIP
+
+**For bug fixes**: run `/prizmkit-retrospective` for structural sync only (skip knowledge injection unless a new TRAPS was discovered). Use `fix(<scope>):` commit prefix.
+
+**a.** Check if feature already committed:
+```bash
+git log --oneline | grep "{{FEATURE_ID}}" | head -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 `.prizm-docs/` architecture index):
+- **Structural sync**: update KEY_FILES/INTERFACES/DEPENDENCIES/file counts for changed modules
+- **Architecture knowledge** (feature sessions only): extract TRAPS, RULES, DECISIONS from completed work into `.prizm-docs/`
+- **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.
+- Stage doc changes: `git add .prizm-docs/`
+⚠️ Do NOT commit here. Only stage.
+- **For bug-fix sessions**: structural sync only, skip knowledge injection unless a genuinely new pitfall was discovered
+
+**c.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
+```bash
+git add <specific-files-created-or-modified>
+git add .prizm-docs/
+```
+
+**d.** Run `/prizmkit-committer` → THE ONLY commit for this feature:
+`feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
+This single commit includes: feature code + tests + .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:
+```bash
+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.

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

@@ -0,0 +1,26 @@
+### Architecture Sync & Commit (SINGLE COMMIT)
+
+**a.** Run `/prizmkit-retrospective` — maintains `.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 `.prizm-docs/` files
+2. **Architecture knowledge** (feature sessions only): Extract TRAPS/RULES/DECISIONS from completed work into `.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 .prizm-docs/`
+⚠️ Do NOT commit here. Only stage.
+
+**b.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
+```bash
+git add <specific-files-created-or-modified>
+git add .prizm-docs/
+```
+
+**c.** Run `/prizmkit-committer` → THE ONLY commit for this feature:
+`feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
+This single commit includes: feature code + tests + .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:
+```bash
+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.

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

@@ -0,0 +1,14 @@
+   - **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 .prizm-docs/)
+     - <trap entries extracted from L1/L2 docs>

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

@@ -0,0 +1,20 @@
+### Build Context Snapshot
+
+```bash
+ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md 2>/dev/null && echo "EXISTS" || echo "MISSING"
+```
+
+If MISSING — build it now:
+1. Read `.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:
+   ```bash
+   find . -maxdepth 2 -type f \( -name "*.js" -o -name "*.ts" -o -name "*.py" -o -name "*.go" -o -name "*.java" -o -name "*.rb" -o -name "*.rs" \) -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/vendor/*' | head -30
+   ```
+   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:
+     ```bash
+     find . -maxdepth 2 -type d -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/__pycache__/*' -not -path '*/vendor/*' | sed -e 's;[^/]*/;|____;g;s;____|; |;g'
+     ```

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

@@ -0,0 +1,3 @@
+   - **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

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

@@ -0,0 +1,24 @@
+### Code Challenge — Critic Agent
+
+**Guard**: Verify critic agent file exists before spawning:
+```bash
+ls {{CRITIC_SUBAGENT_PATH}} 2>/dev/null && echo "CRITIC:READY" || echo "CRITIC:MISSING"
+```
+If CRITIC:MISSING — skip this phase entirely and proceed. Log: "Critic agent not installed — skipping Code Challenge."
+
+Spawn Critic agent (Agent tool, subagent_type="prizm-dev-team-critic", run_in_background=false).
+
+Prompt:
+> "Read {{CRITIC_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
+> **MODE: Code Challenge**
+> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` — Implementation Log section shows what Dev changed.
+> 2. Read `.prizm-docs/root.prizm` and relevant module docs for RULES/PATTERNS.
+> 3. Read the actual source files changed (from Implementation Log).
+> 4. Read comparable existing source files in the same module for style comparison.
+> 5. Challenge code integration quality: style fit, robustness, existing code cohesion, hidden impact.
+> Write `.prizmkit/specs/{{FEATURE_SLUG}}/challenge-report.md` (overwrite) with findings (or 'No significant challenges')."
+
+Wait for Critic to return.
+- Read challenge-report.md. For items marked CRITICAL/HIGH: spawn Dev to fix, then proceed to Review.
+
+**CP-3.5**: Code challenges reviewed and resolved.