prizmkit 1.1.8 → 1.1.9

package/bundled/dev-pipeline/templates/refactor-bootstrap-prompt.md

@@ -0,0 +1,270 @@
+# Dev-Pipeline Refactor Session Bootstrap
+
+## Session Context
+
+- **Pipeline Run ID**: {{RUN_ID}}
+- **Session ID**: {{SESSION_ID}}
+- **Refactor ID**: {{REFACTOR_ID}}
+- **Refactor Title**: {{REFACTOR_TITLE}}
+- **Refactor Type**: {{REFACTOR_TYPE}}
+- **Priority**: {{PRIORITY}}
+- **Complexity**: {{COMPLEXITY}}
+- **Retry Count**: {{RETRY_COUNT}} / {{MAX_RETRIES}}
+- **Previous Session Status**: {{PREV_SESSION_STATUS}}
+- **Resume From Phase**: {{RESUME_PHASE}}
+
+## Your Mission
+
+You are the **refactor session orchestrator**. Execute Refactor {{REFACTOR_ID}}: "{{REFACTOR_TITLE}}".
+
+**CRITICAL SESSION LIFECYCLE RULE**: You MUST NOT exit until ALL work is complete and session-status.json is written. When you spawn subagents, you MUST **wait for each to finish** (run_in_background=false) before proceeding. Do NOT spawn an agent in the background and exit — that kills the session.
+
+**NON-INTERACTIVE MODE**: You are running in headless 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.
+
+**MANDATORY TEAM REQUIREMENT**: You MUST use the `prizm-dev-team` agents (Dev + Reviewer). This is NON-NEGOTIABLE. All implementation and review work MUST be performed by the appropriate team agents (Dev, Reviewer). You are the orchestrator — handle coordination, planning, and commit phases directly.
+
+**REFACTOR DOCUMENTATION POLICY**:
+- **DEFAULT**: Run `/prizmkit-retrospective` with full sync (Job 1 + Job 2), because refactoring changes code structure and interfaces.
+- **SKIP Job 2** only if the refactor is a pure rename with no interface changes.
+- Commit with `refactor(<scope>):` prefix, NOT `feat:` or `fix:`
+
+### Team Definition Reference
+
+- **Team config**: `{{TEAM_CONFIG_PATH}}`
+
+### Refactor Description
+
+{{REFACTOR_DESCRIPTION}}
+
+### Scope
+
+**Files:**
+{{SCOPE_FILES}}
+
+**Modules:**
+{{SCOPE_MODULES}}
+
+### Behavior Preservation
+
+- **Strategy**: {{BEHAVIOR_STRATEGY}}
+- **Existing Tests**:
+{{EXISTING_TESTS}}
+- **New Tests Needed**:
+{{NEW_TESTS_NEEDED}}
+
+### Acceptance Criteria
+
+{{ACCEPTANCE_CRITERIA}}
+
+### Dependencies
+
+{{DEPENDENCIES}}
+
+### App Global Context
+
+{{GLOBAL_CONTEXT}}
+
+## Refactor Artifacts Directory
+
+**ALWAYS** use per-refactor subdirectory `.prizmkit/refactor/{{REFACTOR_ID}}/`:
+
+```
+.prizmkit/refactor/{{REFACTOR_ID}}/
+├── spec.md              ← /prizmkit-plan output (goals, scope, behavior preservation)
+├── plan.md              ← /prizmkit-plan output (change approach, tasks)
+└── refactor-report.md   ← Phase 5 output (generated after commit)
+```
+
+## Execution Instructions
+
+**YOU are the orchestrator. Execute each phase by spawning the appropriate team agent with run_in_background=false.**
+
+## Workflow Checkpoint System
+
+A checkpoint file tracks your progress through this workflow:
+
+**Path**: `{{CHECKPOINT_PATH}}`
+
+**How to use**:
+1. **Before each step**: Read `workflow-checkpoint.json`, verify the previous step has `status: "completed"` or `status: "skipped"`. If not, complete it first.
+2. **After completing a step**: Update the step's `status` to `"completed"` in `workflow-checkpoint.json`.
+
+### Step 1: Initialize
+
+#### Agent Setup
+
+Reference `{{TEAM_CONFIG_PATH}}` for agent definitions:
+- Dev: `{{DEV_SUBAGENT_PATH}}`
+- Reviewer: `{{REVIEWER_SUBAGENT_PATH}}`
+
+Create refactor artifacts directory:
+```bash
+mkdir -p .prizmkit/refactor/{{REFACTOR_ID}}
+```
+
+### Step 2: Pipeline Phases
+
+#### Phase 1: Plan — Specification & Plan Generation
+
+**Goal**: Generate spec.md and plan.md with behavior-preserving task breakdown.
+
+Run `/prizmkit-plan` with `artifact_dir=.prizmkit/refactor/{{REFACTOR_ID}}/`:
+- Description: "{{REFACTOR_TITLE}} — {{REFACTOR_DESCRIPTION}}"
+- The spec.md MUST include:
+  - Goals with acceptance criteria (from the acceptance criteria above)
+  - Scope (files and modules from above)
+  - Behavior Preservation section (strategy: {{BEHAVIOR_STRATEGY}}, existing tests, what must not change)
+- The plan.md MUST include:
+  - Change approach with behavior preservation strategy
+  - Tasks ordered by safety: safe renames first → extractions → structural changes
+  - Every task ends with "run test suite to verify behavior preserved"
+  - Rollback strategy
+
+Resolve any `[NEEDS CLARIFICATION]` markers using the refactor description — do NOT pause for interactive input.
+
+- **CP-RF-1**: Both `spec.md` and `plan.md` exist in `.prizmkit/refactor/{{REFACTOR_ID}}/`
+- **Checkpoint update**: set step `prizmkit-plan` to `"completed"` in `{{CHECKPOINT_PATH}}`
+
+---
+
+#### Phase 2: Implement — Behavior-Preserving Refactoring
+
+**Goal**: Execute all tasks from plan.md while preserving existing behavior.
+
+- Spawn Dev agent (Agent tool, subagent_type="prizm-dev-team-dev", run_in_background=false)
+  Prompt: "Read {{DEV_SUBAGENT_PATH}}. For refactor {{REFACTOR_ID}} ('{{REFACTOR_TITLE}}'):
+  1. Read `.prizmkit/refactor/{{REFACTOR_ID}}/spec.md` and `.prizmkit/refactor/{{REFACTOR_ID}}/plan.md`
+  2. Read `.prizm-docs/` for affected modules (TRAPS, RULES, PATTERNS)
+  3. Before making any changes, run the existing test suite to establish a green baseline
+  4. Execute each task from plan.md in order:
+     - Apply the change
+     - Run the test suite after EVERY task — all tests MUST pass
+     - If tests fail: revert the task, analyze why, try alternative approach
+     - Mark task as [x] in plan.md after tests pass
+  5. Do NOT change behavior — only improve structure
+  6. If the refactor involves multiple files: run `/compact` after completing half the tasks to free context budget. If `/compact` is unavailable, continue without it.
+  7. After all tasks complete, run the full test suite one final time
+  "
+- **Wait for Dev to return**
+- If Dev reports test failures that cannot be resolved after 3 attempts: escalate, write status="failed"
+- **CP-RF-2**: All tasks completed, all tests green
+- **Checkpoint update**: set step `prizmkit-implement` to `"completed"` in `{{CHECKPOINT_PATH}}`
+
+---
+
+#### Phase 3: Review — Code Review & Behavior Verification
+
+**Goal**: Verify refactoring quality and behavior preservation.
+
+- Spawn Reviewer agent (Agent tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false)
+  Prompt: "Read {{REVIEWER_SUBAGENT_PATH}}. For refactor {{REFACTOR_ID}}:
+  1. Read `.prizmkit/refactor/{{REFACTOR_ID}}/spec.md` for goals and behavior preservation contracts
+  2. Read `.prizmkit/refactor/{{REFACTOR_ID}}/plan.md` for architecture decisions and completed tasks
+  3. Run `/prizmkit-code-review` with artifact_dir=.prizmkit/refactor/{{REFACTOR_ID}}/ scoped to CHANGED FILES ONLY (both phases: diagnostic + fix strategy)
+  4. Run full test suite and verify ALL tests pass
+  5. Write integration tests covering all goals from spec.md
+  6. review-report.md will be written to .prizmkit/refactor/{{REFACTOR_ID}}/ by prizmkit-code-review
+  7. Report: number of findings found, or 'no findings' if clean
+  "
+- **Wait for Reviewer to return**
+- **Verdict decision** (L4 responsibility): If findings exist → return to Phase 2 for refinement (max 2 review rounds). If no findings → proceed.
+- **CP-RF-3**: Code review passes, all tests green, behavior preserved
+- **Checkpoint update**: set step `prizmkit-code-review` to `"completed"` in `{{CHECKPOINT_PATH}}`
+
+---
+
+#### Phase 4: Commit & Report
+
+**Goal**: Commit the refactor, update docs, generate report.
+
+**This phase is executed by YOU (the orchestrator), NOT a subagent.**
+
+1. Run `/prizmkit-retrospective` (full sync — Job 1 + Job 2) to update `.prizm-docs/` with structural changes
+
+2. Run `/prizmkit-committer` with:
+   - Commit message: `refactor({{REFACTOR_ID}}): {{REFACTOR_TITLE}}`
+   - Include all refactored files and any new/updated tests
+   - Do NOT push (user will push manually)
+
+3. Write the refactor report to `.prizmkit/refactor/{{REFACTOR_ID}}/refactor-report.md`
+
+   The refactor-report.md MUST contain these sections:
+   - Refactor Summary (ID, title, type, status, phases completed)
+   - What Changed (files modified, structural changes made, diff summary)
+   - Behavior Verification (test suite results before/after, specific tests exercised)
+   - Code Quality Metrics (if measurable: files consolidated, duplication reduced, etc.)
+   - Acceptance Criteria Verification (checklist with pass/fail for each criterion)
+
+4. Write completion summary for downstream dependency context:
+
+   Write `.prizmkit/refactor/{{REFACTOR_ID}}/completion-summary.json` — this is NOT committed to git. The pipeline runner reads it to propagate context to dependent refactors.
+   ```json
+   {
+     "completion_notes": [
+       "<each item: one key structural change that downstream refactors may need to know>",
+       "Example: Extracted shared validation logic into src/utils/validation.ts",
+       "Example: Renamed UserService → AuthService, moved from src/services/ to src/auth/",
+       "Example: Decoupled payment module from user module via PaymentGateway interface"
+     ]
+   }
+   ```
+   Rules: focus on structural changes, new module boundaries, renamed/moved files, changed interfaces. 3-8 notes, each under 120 chars.
+
+- **CP-RF-4**: Commit recorded, refactor-report.md written, .prizm-docs/ updated
+- **Checkpoint update**: set steps `prizmkit-committer` and `refactor-report` to `"completed"` in `{{CHECKPOINT_PATH}}`
+
+### Step 3: Report Session Status
+
+**CRITICAL**: Before this session ends, you MUST write the session status file.
+
+Write to: `{{SESSION_STATUS_PATH}}`
+
+```json
+{
+  "session_id": "{{SESSION_ID}}",
+  "refactor_id": "{{REFACTOR_ID}}",
+  "status": "<success|partial|failed>",
+  "completed_phases": [1, 2, 3, 4],
+  "current_phase": 4,
+  "checkpoint_reached": "CP-RF-4",
+  "errors": [],
+  "can_resume": false,
+  "resume_from_phase": null,
+  "artifacts": {
+    "spec_path": ".prizmkit/refactor/{{REFACTOR_ID}}/spec.md",
+    "plan_path": ".prizmkit/refactor/{{REFACTOR_ID}}/plan.md",
+    "report_path": ".prizmkit/refactor/{{REFACTOR_ID}}/refactor-report.md"
+  },
+  "git_commit": "<commit hash>",
+  "behavior_preserved": true,
+  "timestamp": "{{TIMESTAMP}}"
+}
+```
+
+**Status values**: `success` (all phases done) | `partial` (can resume) | `failed` (unrecoverable)
+
+## Critical Paths
+
+| Resource | Path |
+|----------|------|
+| Team Definition (source of truth) | `{{TEAM_CONFIG_PATH}}` |
+| Refactor Artifacts Dir | `.prizmkit/refactor/{{REFACTOR_ID}}/` |
+| Spec | `.prizmkit/refactor/{{REFACTOR_ID}}/spec.md` |
+| Plan | `.prizmkit/refactor/{{REFACTOR_ID}}/plan.md` |
+| Refactor Report | `.prizmkit/refactor/{{REFACTOR_ID}}/refactor-report.md` |
+| Dev Agent Def | {{DEV_SUBAGENT_PATH}} |
+| Reviewer Agent Def | {{REVIEWER_SUBAGENT_PATH}} |
+| Session Status Output | {{SESSION_STATUS_PATH}} |
+| Workflow Checkpoint | {{CHECKPOINT_PATH}} |
+| Project Root | {{PROJECT_ROOT}} |
+
+## Reminders
+
+- **MANDATORY**: Use `prizm-dev-team` agents — single-agent execution is FORBIDDEN
+- **Behavior preservation is the #1 priority**: If tests break, stop and fix before proceeding
+- **Run tests after EVERY task** — not just at the end
+- Use `/prizmkit-plan` with `artifact_dir=.prizmkit/refactor/{{REFACTOR_ID}}/` for spec + plan generation
+- **Commit with** `refactor(<scope>):` prefix, NOT `feat:` or `fix:`
+- **Run full retrospective** (Job 1 + Job 2) — refactoring changes code structure
+- ALWAYS write session-status.json before exiting
+- Do NOT use `run_in_background=true` when spawning agents

package/bundled/dev-pipeline/templates/refactor-list-schema.json

@@ -164,9 +164,10 @@
               "in_progress",
               "completed",
               "failed",
-              "skipped"
+              "skipped",
+              "auto_skipped"
             ],
-            "description": "Refactor status"
+            "description": "Refactor status. Subset of feature status enum."
           },
           "model": {
             "type": "string",
@@ -176,6 +177,13 @@
             "type": "integer",
             "description": "Estimated number of lines affected by this refactor"
           },
+          "completion_notes": {
+            "type": "array",
+            "items": {
+              "type": "string"
+            },
+            "description": "AI-generated summary of key changes from this refactor session. Used to provide rich dependency context to downstream refactors. Each item is a concise statement about what was refactored (e.g. modules extracted, files restructured, interfaces changed)."
+          },
           "critic": {
             "type": "boolean",
             "description": "Enable adversarial critic review for this refactor. Default: true for critical/high priority refactors, false for others.",

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

@@ -1,6 +1,8 @@
 ## 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:
+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.

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

@@ -6,4 +6,5 @@
 | 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/templates/sections/feature-context.md

@@ -15,6 +15,8 @@
 
 ### 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

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

@@ -1,6 +1,11 @@
 ### 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.
+**Bug Fix Documentation Policy**:
+- DEFAULT: Run `/prizmkit-retrospective` with structural sync only (update file counts, interfaces, dependencies). Skip knowledge injection.
+- UPDATE DOCS (run full retrospective — Job 1 + Job 2) when bug fix causes: interface signature changes, dependency additions/removals, observable behavior changes to existing features, or newly discovered TRAPs.
+- Simple bugs: No new spec.md/plan.md needed. Use fast path.
+- Complex bugs (multi-module, cascading): Use `/prizmkit-plan` with `artifact_dir=.prizmkit/bugfix/<BUG_ID>/`.
+- Commit prefix: `fix(<scope>):` (not `feat:`).
 
 **a.** Check if feature already committed:
 ```bash
@@ -15,7 +20,7 @@ git log --oneline | grep "{{FEATURE_ID}}" | head -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.
 - 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
+- **For bug-fix sessions**: structural sync (Job 1) by default. Run knowledge injection (Job 2) when the fix causes interface signature changes, dependency additions/removals, observable behavior changes, or reveals new TRAPs
 
 **c.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
 ```bash
@@ -35,5 +40,27 @@ 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, update `workflow-checkpoint.json` — set step `prizmkit-retrospective` to `"completed"`. After `/prizmkit-committer` completes, set step `prizmkit-committer` to `"completed"`.

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

@@ -25,5 +25,27 @@ 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, update `workflow-checkpoint.json` — set step `prizmkit-retrospective` to `"completed"`. After `/prizmkit-committer` completes, set step `prizmkit-committer` to `"completed"`.

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

@@ -7,7 +7,7 @@ You just implemented this feature — you know the project's tech stack and buil
 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:
+   - **Cannot build locally** (missing system-level deps you cannot install) → Generate `.prizmkit/deploy.md` with:
      ```
      # Local Development Setup
 
@@ -23,7 +23,7 @@ You just implemented this feature — you know the project's tech stack and buil
      ## Verify
      [how to confirm the app is running correctly]
      ```
-     Record: `## Deploy Verification: PARTIAL — see DEPLOY.md for missing prerequisites`
+     Record: `## Deploy Verification: PARTIAL — see .prizmkit/deploy.md for missing prerequisites`
 
 Deploy verification does NOT block the commit, but you MUST attempt it.
 

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

@@ -11,16 +11,18 @@
 
 Wait for Reviewer to return.
 
-**Gate Check — Review Notes**:
-After Reviewer agent returns, verify the Review Notes were written:
+**Gate Check — Review Report**:
+After Reviewer agent returns, verify the review report was written:
 ```bash
-grep -q "## Review Notes" .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md && echo "GATE:PASS" || echo "GATE:MISSING"
+grep -q "## Findings" .prizmkit/specs/{{FEATURE_SLUG}}/review-report.md && echo "GATE:PASS" || echo "GATE:MISSING"
 ```
-If GATE:MISSING — send message to Reviewer (re-spawn if needed): "Write the '## Review Notes' section to context-snapshot.md with structured Fix Instructions. Include: verdict, findings with Root Cause/Impact/Fix Strategy/Code Guidance/Verification, and Re-Review Expectations."
+If GATE:MISSING — send message to Reviewer (re-spawn if needed): "Write review-report.md to .prizmkit/specs/{{FEATURE_SLUG}}/ with findings."
 
-- If NEEDS_FIXES: spawn Dev to fix (Dev reads Fix Instructions in snapshot), re-run Review (max 3 rounds)
+**Verdict decision** (L4 responsibility): Read review-report.md findings count. If findings exist → NEEDS_FIXES. If no findings → PASS.
 
-**CP-3**: Tests pass, verdict is not NEEDS_FIXES.
+- If NEEDS_FIXES: spawn Dev to fix (Dev reads Fix Instructions in review-report.md), re-run Review (max 3 rounds)
+
+**CP-3**: Tests pass, no unresolved findings.
 
 
 **Checkpoint update**: Update `workflow-checkpoint.json` — set step `prizmkit-code-review` to `"completed"`.

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

@@ -11,18 +11,20 @@
 
 Wait for Reviewer to return.
 
-**Gate Check — Review Notes**:
-After Reviewer agent returns, verify the Review Notes were written:
+**Gate Check — Review Report**:
+After Reviewer agent returns, verify the review report was written:
 ```bash
-grep -q "## Review Notes" .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md && echo "GATE:PASS" || echo "GATE:MISSING"
+grep -q "## Findings" .prizmkit/specs/{{FEATURE_SLUG}}/review-report.md && echo "GATE:PASS" || echo "GATE:MISSING"
 ```
-If GATE:MISSING — send message to Reviewer (re-spawn if needed): "Write the '## Review Notes' section to context-snapshot.md with structured Fix Instructions. Include: verdict, findings with Root Cause/Impact/Fix Strategy/Code Guidance/Verification, and Re-Review Expectations."
+If GATE:MISSING — send message to Reviewer (re-spawn if needed): "Write review-report.md to .prizmkit/specs/{{FEATURE_SLUG}}/ with findings."
+
+**Verdict decision** (L4 responsibility): Read review-report.md findings count. If findings exist → NEEDS_FIXES. If no findings → PASS.
 
 - If NEEDS_FIXES: spawn Dev to fix with this prompt:
   > {{AGENT_PROMPT_DEV_FIX}}
   Then re-run Review (max 3 rounds).
 
-**CP-3**: Integration tests pass, verdict is not NEEDS_FIXES.
+**CP-3**: Integration tests pass, no unresolved findings.
 
 
 **Checkpoint update**: Update `workflow-checkpoint.json` — set step `prizmkit-code-review` to `"completed"`.

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

@@ -37,7 +37,7 @@ If `EXISTING_CODE` is non-empty: your spec/plan/tasks must reflect this existing
    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 1 — Task Brief**: task 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'
@@ -67,8 +67,8 @@ 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-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)
+- 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.
 

package/bundled/skills/_metadata.json

@@ -1,11 +1,11 @@
 {
-  "version": "1.1.8",
+  "version": "1.1.9",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",
       "tier": "foundation",
       "category": "prizmkit-skill",
-      "hasAssets": true,
+      "hasAssets": false,
       "hasScripts": false
     },
     "prizmkit-init": {
@@ -16,19 +16,12 @@
       "hasScripts": false
     },
     "prizmkit-plan": {
-      "description": "Specify and plan features: natural language → spec.md → plan.md with architecture and executable tasks.",
+      "description": "Specify and plan tasks: natural language → spec.md → plan.md with architecture and executable tasks.",
       "tier": "1",
       "category": "prizmkit-skill",
       "hasAssets": true,
       "hasScripts": false
     },
-    "prizmkit-analyze": {
-      "description": "Cross-document consistency analysis for spec.md and plan.md. Check if spec and plan are aligned, validate documents before coding.",
-      "tier": "1",
-      "category": "prizmkit-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
     "prizmkit-implement": {
       "description": "Execute implementation following plan.md Tasks section with TDD approach.",
       "tier": "1",
@@ -65,19 +58,12 @@
       "hasScripts": false
     },
     "prizmkit-deploy": {
-      "description": "Generate or update deployment documentation (DEPLOY.md) by scanning project state and deploy strategy. Fully autonomous.",
+      "description": "Generate or update deployment documentation (.prizmkit/deploy.md) by scanning project state and deploy strategy. On-demand skill.",
       "tier": "1",
       "category": "prizmkit-skill",
       "hasAssets": true,
       "hasScripts": false
     },
-    "prizmkit-verify": {
-      "description": "Automated framework verification for PrizmKit's 4-layer architecture. Checks structural integrity, contract consistency, and cross-scenario alignment.",
-      "tier": "1",
-      "category": "prizmkit-skill",
-      "hasAssets": false,
-      "hasScripts": true
-    },
     "feature-workflow": {
       "description": "One-stop entry point for feature development. Orchestrates feature-planner → feature-pipeline-launcher → background execution. Handles multi-feature batch development from a single request.",
       "tier": "companion",
@@ -175,7 +161,6 @@
         "prizmkit-init",
         "prizmkit-prizm-docs",
         "prizmkit-plan",
-        "prizmkit-analyze",
         "prizmkit-implement",
         "prizmkit-code-review",
         "prizmkit-committer",
@@ -191,8 +176,7 @@
         "refactor-planner",
         "refactor-pipeline-launcher",
         "bug-fix-workflow",
-        "recovery-workflow",
-        "prizmkit-verify"
+        "recovery-workflow"
       ]
     },
     "minimal": {
@@ -202,7 +186,6 @@
         "prizmkit-init",
         "prizmkit-prizm-docs",
         "prizmkit-plan",
-        "prizmkit-analyze",
         "prizmkit-implement",
         "prizmkit-code-review",
         "prizmkit-committer",