prizmkit 1.1.118 → 1.1.120

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

@@ -50,7 +50,7 @@ You are running in **headless non-interactive mode** with a FINITE context windo
 
 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 Phase 1-2 builds it, ALWAYS read context-snapshot.md instead of re-reading individual source files
+1. **context-snapshot.md is your single source of truth** — After Phase 1-2 makes it available, use it instead of re-reading individual source files. If you just created or updated it in this session, continue from the in-context content; read it only when resuming/continuing, after context compaction/loss, or when handing work to a subagent.
 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. **Never re-read unmodified files** — Once you have read a file into context, do NOT read it again unless it was modified by an Edit/Write operation after your last read. Use platform file/search tools for targeted lookup; when shell-free helper lookup is needed, run `{{RUNTIME_HELPER_CMD}} text search <file> --pattern "<pattern>" --json`, then read only the smallest bounded range with the platform file-reading tool instead of full-file Read. Before issuing a Read, ask yourself: "Have I read this file before, and has it changed since?" If the answer is "no, it hasn't changed" — do NOT read it. This applies to all files including those summarized in context-snapshot.md Section 4. Reviewer subagents must receive context-snapshot.md and rely on it rather than independently re-reading the same files the orchestrator already read.
 4. **Stay focused** — Do NOT explore code unrelated to this feature. No curiosity-driven reads.
@@ -205,14 +205,13 @@ Before starting, check plan.md Tasks:
 
 **Build artifacts rule**: After any build/compile command, ensure output is in `.gitignore`. Never commit binaries/build output.
 
-**3a.** Run `/prizmkit-implement` directly — you (the orchestrator) execute the full cycle:
-- Read plan.md Tasks from `.prizmkit/specs/{{FEATURE_SLUG}}/`
-- Use context-snapshot.md Section 4 File Manifest for targeted reads — do NOT re-read files already summarized there
+**3a.** Run `/prizmkit-implement` directly:
+- Continue from the `spec.md` / `plan.md` / `context-snapshot.md` content you created in Phase 1-2; do not re-read self-authored artifacts just because implementation starts
+- Re-read `plan.md` or `context-snapshot.md` only when resuming/continuing, when current context was compacted or lost, or when task checkbox state may have changed outside this session
+- If implementation is delegated to a Dev subagent, the subagent must read `spec.md` if the artifact exists, plus `plan.md` and `context-snapshot.md`, before editing
+- Use context-snapshot.md Section 4 File Manifest for targeted source reads; avoid re-reading source files already summarized there unless they changed after the snapshot
 - Implements task-by-task, marking each `[x]` immediately
-- Creates/updates L2 `.prizm` docs when creating new modules
-- Defers scoped/full test execution until after the code-review loop completes
-- Preserves Reviewer behavior; only the top-level implementation Dev handoff is removed
-- If plan.md has >5 tasks: update checkpoints after every 3 tasks
+- Remeber to update checkpoints after finishing a series of tasks
 
 **3b. Focused checks only (no test gate here)**:
 - During implementation, do not run mandatory periodic or full-suite tests.
@@ -507,7 +506,6 @@ Rules for writing completion notes:
 |----------|------|
 | Feature Artifacts Dir | `.prizmkit/specs/{{FEATURE_SLUG}}/` |
 | Context Snapshot | `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` |
-| Team Config | `{{TEAM_CONFIG_PATH}}` |
 | Project Root | {{PROJECT_ROOT}} |
 | Feature List Path | {{FEATURE_LIST_PATH}} |
 

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

@@ -12,9 +12,9 @@ If `FAST_PATH=true`, skip this phase intentionally:
 
 Then continue to the next checkpoint step.
 
-Otherwise, run `/prizmkit-code-review` with `artifact_dir=.prizmkit/bugfix/{{BUG_ID}}/`.
+Otherwise, run `/prizmkit-code-review` with `artifact_dir=.prizmkit/bugfix/{{BUG_ID}}/`. The code-review skill loads its skill-owned `references/reviewer-agent-prompt.md` prompt and launches the internal reviewer in `current-workspace / active-checkout / no-worktree` mode.
 
-The skill runs its internal Reviewer Agent → filter → orchestrator fix loop and writes `review-report.md`.
+The skill runs its internal Reviewer Agent → filter → orchestrator fix loop and writes `review-report.md`. Do not request worktree isolation or use `.claude/worktrees/...` / `.prizmkit/state/worktrees/...`; outer runner `USE_WORKTREE` settings do not permit review subagent isolation.
 
 **Gate Check — Review Report**:
 

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

@@ -4,7 +4,7 @@ You are running in **headless non-interactive mode** with a FINITE context windo
 
 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
+1. **context-snapshot.md is your single source of truth** — After it is available, use it instead of re-reading individual source files. If you just created or updated it in this session, continue from the in-context content; read it only when resuming/continuing, after context compaction/loss, or when handing work to a subagent.
 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. **Never re-read unmodified files** — Once you have read a file into context, do NOT read it again unless it was modified by an Edit/Write operation after your last read. Use platform file/search tools for targeted lookup; when shell-free helper lookup is needed, run `{{RUNTIME_HELPER_CMD}} text search <file> --pattern "<pattern>" --json`, then read only the smallest bounded range with the platform file-reading tool instead of full-file Read. Before issuing a Read, ask yourself: "Have I read this file before, and has it changed since?" If the answer is "no, it hasn't changed" — do NOT read it. This applies to all files including those summarized in context-snapshot.md Section 4. Reviewer subagents must receive context-snapshot.md and rely on it rather than independently re-reading the same files the orchestrator already read.
 4. **Stay focused** — Do NOT explore code unrelated to this feature. No curiosity-driven reads.

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

@@ -4,5 +4,4 @@
 |----------|------|
 | Feature Artifacts Dir | `.prizmkit/specs/{{FEATURE_SLUG}}/` |
 | Context Snapshot | `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` |
-| Reviewer Agent Def | {{REVIEWER_SUBAGENT_PATH}} |
 | Project Root | {{PROJECT_ROOT}} |

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

@@ -4,7 +4,5 @@
 |----------|------|
 | Feature Artifacts Dir | `.prizmkit/specs/{{FEATURE_SLUG}}/` |
 | Context Snapshot | `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` |
-| Team Config | `{{TEAM_CONFIG_PATH}}` |
-| Reviewer Agent Def | {{REVIEWER_SUBAGENT_PATH}} |
 | Project Root | {{PROJECT_ROOT}} |
 | Feature List Path | {{FEATURE_LIST_PATH}} |

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

@@ -1,12 +1,17 @@
 ### Architecture Sync & Commit (SINGLE COMMIT) — DO NOT SKIP
 
-**a.** Check if feature already committed:
+**a.** Check if feature already committed by inspecting recent git history for `{{FEATURE_ID}}`:
 ```bash
 git log --oneline
 ```
 - 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.
 
+**Feature Documentation Policy**:
+- Run `/prizmkit-retrospective` before commit to update `.prizmkit/prizm-docs/` with durable structural knowledge from this feature.
+- Capture architecture knowledge when the feature adds interfaces, dependencies, observable behavior, modules, or durable TRAPS/RULES/DECISIONS.
+- Commit prefix: `feat({{FEATURE_ID}}):`.
+
 **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/`
@@ -32,6 +37,8 @@ git status --short
 ```
 Working tree MUST be clean after this step. If any feature-related files remain, stage them explicitly and amend the SAME commit with `git commit --amend --no-edit`; do NOT create a separate commit.
 
+**Exception**: `session-summary.md` in the artifact directory is a local cross-session artifact generated by `/prizmkit-committer` — it is NOT committed to git. Ignore it in the clean-tree check.
+
 **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.

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

@@ -11,14 +11,13 @@ Before starting, check plan.md Tasks:
 
 **Build artifacts rule**: After any build/compile command, ensure output is in `.gitignore`. Never commit binaries/build output.
 
-**3a.** Run `/prizmkit-implement` directly — you (the orchestrator) execute the full cycle:
-- Read plan.md Tasks from `.prizmkit/specs/{{FEATURE_SLUG}}/`
-- Use context-snapshot.md Section 4 File Manifest for targeted reads — do NOT re-read files already summarized there
+**3a.** Run `/prizmkit-implement` directly:
+- Continue from the `spec.md` / `plan.md` / `context-snapshot.md` content you created in Phase 1-2; do not re-read self-authored artifacts just because implementation starts
+- Re-read `plan.md` or `context-snapshot.md` only when resuming/continuing, when current context was compacted or lost, or when task checkbox state may have changed outside this session
+- If implementation is delegated to a Dev subagent, the subagent must read `spec.md` if the artifact exists, plus `plan.md` and `context-snapshot.md`, before editing
+- Use context-snapshot.md Section 4 File Manifest for targeted source reads; avoid re-reading source files already summarized there unless they changed after the snapshot
 - Implements task-by-task, marking each `[x]` immediately
-- Creates/updates L2 `.prizm` docs when creating new modules
-- Defers scoped/full test execution until after the code-review loop completes
-- Preserves Reviewer behavior; only the top-level implementation Dev handoff is removed
-- If plan.md has >5 tasks: update checkpoints after every 3 tasks
+- Remeber to update checkpoints after finishing a series of tasks
 
 **3b. Focused checks only (no test gate here)**:
 - During implementation, do not run mandatory periodic or full-suite tests.

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

@@ -11,14 +11,13 @@ Before starting, check plan.md Tasks:
 
 **Build artifacts rule**: After any build/compile command, ensure output is in `.gitignore`. Never commit binaries/build output.
 
-**3a.** Run `/prizmkit-implement` directly — you (the orchestrator) execute the full cycle:
-- Read plan.md Tasks from `.prizmkit/specs/{{FEATURE_SLUG}}/`
-- Use context-snapshot.md Section 4 File Manifest for targeted reads — do NOT re-read files already summarized there
+**3a.** Run `/prizmkit-implement` directly:
+- Continue from the `spec.md` / `plan.md` / `context-snapshot.md` content you created in Phase 1-2; do not re-read self-authored artifacts just because implementation starts
+- Re-read `plan.md` or `context-snapshot.md` only when resuming/continuing, when current context was compacted or lost, or when task checkbox state may have changed outside this session
+- If implementation is delegated to a Dev subagent, the subagent must read `spec.md` if the artifact exists, plus `plan.md` and `context-snapshot.md`, before editing
+- Use context-snapshot.md Section 4 File Manifest for targeted source reads; avoid re-reading source files already summarized there unless they changed after the snapshot
 - Implements task-by-task, marking each `[x]` immediately
-- Creates/updates L2 `.prizm` docs when creating new modules
-- Defers scoped/full test execution until after the code-review loop completes
-- Preserves Reviewer behavior; only the top-level implementation Dev handoff is removed
-- If plan.md has >5 tasks: update checkpoints after every 3 tasks
+- Remeber to update checkpoints after finishing a series of tasks
 
 **3b. Focused checks only (no test gate here)**:
 - During implementation, do not run mandatory periodic or full-suite tests.

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

@@ -6,8 +6,10 @@
 - Follow Context Budget Rules §10 after build/compile commands.
 
 **3a.** Run `/prizmkit-implement` — this handles the implementation cycle:
-- Reads plan.md Tasks section from `.prizmkit/specs/{{FEATURE_SLUG}}/`
-- Reads context from `context-snapshot.md` (Prizm docs, TRAPS, file manifest)
+- Continue from the plan/context you just created; do not re-read self-authored artifacts just because implementation starts
+- Re-read plan.md or `context-snapshot.md` only when resuming/continuing, when current context was compacted or lost, or when task checkbox state may have changed outside this session
+- If implementation is delegated to a subagent, the subagent must read `plan.md` and `context-snapshot.md` before editing
+- Uses context from `context-snapshot.md` (Prizm docs, TRAPS, file manifest) for targeted source reads; avoid re-reading source files already summarized there unless they changed after the snapshot
 - Implements task-by-task, marking each `[x]` immediately
 - Creates/updates L2 `.prizm` docs when creating new modules or significantly modifying existing ones — AI selectively decides which modules warrant L2 based on complexity and importance
 - Does not run the scoped/full test gate; testing happens after code review in the PrizmKit Test phase

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

@@ -2,9 +2,9 @@
 
 Review the completed implementation before the scoped feature test gate runs. Use `artifact_dir=.prizmkit/specs/{{FEATURE_SLUG}}/` so the code-review skill can read spec, plan, context snapshot, implementation log, and current diff artifacts. Do not require or read a prior `/prizmkit-test` report here; test generation and test-fix looping happen in the next phase.
 
-Run `/prizmkit-code-review` with `artifact_dir=.prizmkit/specs/{{FEATURE_SLUG}}/`.
+Run `/prizmkit-code-review` with `artifact_dir=.prizmkit/specs/{{FEATURE_SLUG}}/`. The code-review skill loads its skill-owned `references/reviewer-agent-prompt.md` prompt and launches the internal reviewer in `current-workspace / active-checkout / no-worktree` mode.
 
-The skill runs an internal review-fix loop (Reviewer Agent → filter → orchestrator fix, max 3 rounds) and writes `review-report.md` to the artifact directory.
+The skill runs an internal review-fix loop (Reviewer Agent → filter → orchestrator fix, max 3 rounds) and writes `review-report.md` to the artifact directory. Do not request worktree isolation or use `.claude/worktrees/...` / `.prizmkit/state/worktrees/...`; outer runner `USE_WORKTREE` settings do not permit review subagent isolation.
 
 **Gate Check — Review Report**:
 After `/prizmkit-code-review` returns, verify the review report:

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

@@ -2,9 +2,11 @@
 
 Review the completed implementation before the scoped feature test gate runs. Use `artifact_dir=.prizmkit/specs/{{FEATURE_SLUG}}/` so the code-review skill can read spec, plan, context snapshot, implementation log, and current diff artifacts. Do not require or read a prior `/prizmkit-test` report here; test generation and test-fix looping happen in the next phase.
 
-Run `/prizmkit-code-review` with `artifact_dir=.prizmkit/specs/{{FEATURE_SLUG}}/`.
+Run `/prizmkit-code-review` with `artifact_dir=.prizmkit/specs/{{FEATURE_SLUG}}/`. The code-review skill loads its skill-owned `references/reviewer-agent-prompt.md` prompt and launches the internal reviewer in `current-workspace / active-checkout / no-worktree` mode.
 
-The skill runs an internal review-fix loop (Reviewer Agent → filter → orchestrator fix, max 3 rounds) and writes `review-report.md` to the artifact directory.
+If the reviewer spawn fails with team/config/lock errors, retry at most once. If the second attempt fails, do not keep spawning variants and do not enter report-polling loops for review markers; write `failure-log.md` with the spawn error and use the documented inline fallback only when safe.
+
+The skill runs an internal review-fix loop (Reviewer Agent → filter → orchestrator fix, max 3 rounds) and writes `review-report.md` to the artifact directory. Do not request worktree isolation or use `.claude/worktrees/...` / `.prizmkit/state/worktrees/...`; outer runner `USE_WORKTREE` settings do not permit review subagent isolation.
 
 **Gate Check — Review Report**:
 After `/prizmkit-code-review` returns, verify the review report:

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

@@ -9,6 +9,15 @@ Check existing artifacts first:
 - `context-snapshot.md` exists → use it directly, skip context snapshot building
 - Some missing → generate only missing files
 
+Before planning, check whether feature code already exists in the project (use the helper to search source directories identified from `root.prizm` or the project tree scan):
+```bash
+{{RUNTIME_HELPER_CMD}} text search . --pattern "{{FEATURE_SLUG}}" --json
+```
+
+Record result as `EXISTING_CODE` (helper `match` entries for source files, or empty; ignore `.prizmkit/` artifact matches).
+
+If `EXISTING_CODE` is non-empty: your spec/plan/tasks must reflect this existing implementation — document what exists, identify gaps, and do NOT re-implement what is already done.
+
 **Step A — Build Context Snapshot** (skip if `context-snapshot.md` already exists):
 
 1. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 prizm docs
@@ -60,4 +69,15 @@ Before proceeding past CP-1, verify:
 
 **CP-1**: Both spec.md and plan.md exist.
 
+### Plan Self-Check — Orchestrator Direct
+
+Do not spawn a top-level Reviewer subagent for planning analysis. Perform a bounded self-check before implementation:
+
+1. Re-read only `context-snapshot.md`, `spec.md`, and `plan.md`.
+2. Cross-check spec.md and plan.md Tasks against the feature description and Verification Gates in the Task Contract.
+3. Verify the plan references the File Manifest and avoids unrelated work.
+4. If you find CRITICAL issues, fix ONLY those issues in spec.md/plan.md before continuing.
+
+**CP-1.5**: Plan self-check complete; no CRITICAL plan issues remain.
+
 

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

@@ -1,8 +1,8 @@
 ### Phase 3: Review — Code Review & Behavior Verification
 
-Run `/prizmkit-code-review` directly with `artifact_dir=.prizmkit/refactor/{{REFACTOR_ID}}/`.
+Run `/prizmkit-code-review` directly with `artifact_dir=.prizmkit/refactor/{{REFACTOR_ID}}/`. The code-review skill loads its skill-owned `references/reviewer-agent-prompt.md` prompt and launches the internal reviewer in `current-workspace / active-checkout / no-worktree` mode.
 
-Do not spawn a top-level Reviewer subagent. The code-review skill owns its internal Reviewer Agent → filter → orchestrator fix loop.
+Do not spawn a top-level Reviewer subagent. The code-review skill owns its internal Reviewer Agent → filter → orchestrator fix loop. Do not request worktree isolation or use `.claude/worktrees/...` / `.prizmkit/state/worktrees/...`; outer runner `USE_WORKTREE` settings do not permit review subagent isolation.
 
 **Gate Check — Review Report**: