prizmkit 1.1.0 → 1.1.3

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

@@ -10,20 +10,19 @@ If CRITIC:MISSING — skip this phase entirely and proceed. Log: "Critic agent n
 
 **If {{CRITIC_COUNT}} = 1 → Single Critic** (skip to CP-2.5 after this):
 
-Spawn Critic agent (Agent tool, subagent_type="prizm-dev-team-critic", run_in_background=false).
+**Spawn Agent**:
+| Parameter | Value |
+|-----------|-------|
+| subagent_type | prizm-dev-team-critic |
+| mode | plan |
+| run_in_background | false |
 
-Prompt:
-> "Read {{CRITIC_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
-> **MODE: Plan Challenge**
-> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — Section 3 has project context, Section 4 has file manifest.
-> 2. Read `.prizm-docs/root.prizm` and relevant L1/L2 docs for affected modules.
-> 3. Read existing source files in the modules this plan touches.
-> 4. Challenge plan.md against the project's existing architecture, patterns, and style.
-> Write `.prizmkit/specs/{{FEATURE_SLUG}}/challenge-report.md` with findings (or 'No significant challenges')."
+**Prompt**:
+> {{AGENT_PROMPT_CRITIC_PLAN_CHALLENGE}}
 
 **If {{CRITIC_COUNT}} = 3 → Multi-Critic Voting** (skip Single Critic above):
 
-Spawn 3 Critic agents sequentially (each with run_in_background=false), each with a different focus lens:
+Spawn 3 Critic agents sequentially (each with mode="plan", run_in_background=false), each with a different focus lens:
 
 Critic-A prompt (append to base prompt above):
 > "**Focus Lens: Architecture & Scalability.** Prioritize: architectural pattern fit, scalability implications, over-engineering risks, component boundary design.

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

@@ -6,16 +6,15 @@ ls {{CRITIC_SUBAGENT_PATH}} 2>/dev/null && echo "CRITIC:READY" || echo "CRITIC:M
 ```
 If CRITIC:MISSING — skip this phase entirely and proceed. Log: "Critic agent not installed — skipping Plan Challenge."
 
-Spawn Critic agent (Agent tool, subagent_type="prizm-dev-team-critic", run_in_background=false).
+**Spawn Agent**:
+| Parameter | Value |
+|-----------|-------|
+| subagent_type | prizm-dev-team-critic |
+| mode | plan |
+| run_in_background | false |
 
-Prompt:
-> "Read {{CRITIC_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
-> **MODE: Plan Challenge**
-> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — Section 3 has project context, Section 4 has file manifest.
-> 2. Read `.prizm-docs/root.prizm` and relevant L1/L2 docs for affected modules.
-> 3. Read existing source files in the modules this plan touches.
-> 4. Challenge plan.md against the project's existing architecture, patterns, and style.
-> Write `.prizmkit/specs/{{FEATURE_SLUG}}/challenge-report.md` with findings (or 'No significant challenges')."
+**Prompt**:
+> {{AGENT_PROMPT_CRITIC_PLAN_CHALLENGE}}
 
 Wait for Critic to return.
 - Read challenge-report.md. For items marked CRITICAL/HIGH: decide whether to adjust plan.md or document why the plan stands.

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

@@ -2,17 +2,14 @@
 
 **Build artifacts rule** (passed to Dev): After any build/compile command (`go build`, `npm run build`, `tsc`, etc.), ensure the output binary or build directory is in `.gitignore`. Never commit compiled binaries, build output, or generated artifacts.
 
-Spawn Dev subagent (Agent tool, subagent_type="prizm-dev-team-dev", run_in_background=false).
+**Spawn Agent**:
+| Parameter | Value |
+|-----------|-------|
+| subagent_type | prizm-dev-team-dev |
+| run_in_background | false |
 
-Prompt:
-> "Read {{DEV_SUBAGENT_PATH}}. Implement feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}).
-> **IMPORTANT**: Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — Section 3 has Prizm Context (TRAPS/RULES), Section 4 has File Manifest with paths and interfaces.
-> ⚠️ DO NOT re-read source files already listed in Section 4 File Manifest unless you need implementation detail beyond the interface summary.
-> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` for full context.
-> 2. Run `/prizmkit-implement` to execute the tasks in plan.md. Use `TEST_CMD=<TEST_CMD>` for testing. Baseline failures: `BASELINE_FAILURES=<BASELINE_FAILURES>`.
-> 3. After implement completes, verify the '## Implementation Log' section was written to context-snapshot.md.
-> 4. Do NOT execute any git commands (no git add/commit/reset/push).
-> Do NOT exit until all tasks are [x] and the '## Implementation Log' section is written in context-snapshot.md."
+**Prompt**:
+> {{AGENT_PROMPT_DEV_IMPLEMENT}}
 
 Wait for Dev to return. All tasks must be `[x]`, tests pass.
 

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

@@ -9,17 +9,14 @@ grep -c '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/plan.md 2>/dev/null || true
 - If result is `0` (all tasks already `[x]`) → **SKIP this phase**, go directly to Review. Do NOT spawn Dev.
 - If result is non-zero → spawn Dev agent below.
 
-Spawn Dev agent (Agent tool, subagent_type="prizm-dev-team-dev", run_in_background=false).
+**Spawn Agent**:
+| Parameter | Value |
+|-----------|-------|
+| subagent_type | prizm-dev-team-dev |
+| run_in_background | false |
 
-Prompt:
-> "Read {{DEV_SUBAGENT_PATH}}. Implement feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}).
-> **IMPORTANT**: Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — Section 3 has Prizm Context (TRAPS/RULES), Section 4 has File Manifest with paths and interfaces.
-> ⚠️ DO NOT re-read source files already listed in Section 4 File Manifest unless you need implementation detail beyond the interface summary.
-> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` for full context.
-> 2. Run `/prizmkit-implement` to execute the tasks in plan.md. Use `TEST_CMD=<TEST_CMD>` for testing. Baseline failures: `BASELINE_FAILURES=<BASELINE_FAILURES>`.
-> 3. After implement completes, verify the '## Implementation Log' section was written to context-snapshot.md.
-> 4. Do NOT execute any git commands (no git add/commit/reset/push).
-> Do NOT exit until all tasks are [x] and the '## Implementation Log' section is written in context-snapshot.md."
+**Prompt**:
+> {{AGENT_PROMPT_DEV_IMPLEMENT}}
 
 **Gate Check — Implementation Log**:
 After Dev agent returns, verify the Implementation Log was written:
@@ -31,11 +28,7 @@ If GATE:MISSING — send message to Dev (re-spawn if needed): "Write the '## Imp
 Wait for Dev to return. **If Dev times out before all tasks are `[x]`**:
 1. Check progress: `grep -c '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/plan.md`
 2. If any tasks remain: re-spawn Dev with this recovery prompt:
-   > "Read {{DEV_SUBAGENT_PATH}}. You are resuming implementation of feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}).
-   > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` — Section 4 has File Manifest, 'Implementation Log' (if present) shows what was already done.
-   > 2. Run `git diff HEAD` to see actual code changes already made.
-   > 3. Run `/prizmkit-implement` to complete the remaining `[ ]` tasks. Use `TEST_CMD=<TEST_CMD>` for testing.
-   > 4. Do NOT execute any git commands."
+   > {{AGENT_PROMPT_DEV_RESUME}}
 3. Max 2 recovery retries. After 2 failures, orchestrator implements remaining tasks directly.
 
 All tasks `[x]`, tests pass.

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

@@ -1,18 +1,13 @@
 ### Review + Test — Reviewer Subagent
 
-Spawn Reviewer subagent (Agent tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false).
+**Spawn Agent**:
+| Parameter | Value |
+|-----------|-------|
+| subagent_type | prizm-dev-team-reviewer |
+| run_in_background | false |
 
-Prompt:
-> "Read {{REVIEWER_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
-> **IMPORTANT**: Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST.
-> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`:
->    - Section 3: Prizm Context (RULES, PATTERNS to check against)
->    - Section 4: File Manifest (original file structure)
->    - '## Implementation Log': what Dev changed, key decisions, discoveries
-> 2. Run prizmkit-code-review (both phases): Phase 1 diagnostic review (spec compliance, code quality, correctness), then Phase 2 fix strategy formulation for any findings. Read ONLY files listed in Implementation Log for diagnosis; MAY read additional files for impact analysis.
-> 3. Run the full test suite — **ONLY if the Implementation Log does not already confirm all tests passing**. If the log states tests passed, trust it and skip the re-run. When running: `$TEST_CMD 2>&1 | tee /tmp/review-test-out.txt | tail -20`, then grep the file for details — do NOT re-run the suite multiple times. Write and execute integration tests covering all user stories.
-> 4. Write structured '## Review Notes' to context-snapshot.md with Fix Instructions (Root Cause, Impact, Fix Strategy, Code Guidance, Verification for each finding) and Re-Review Expectations.
-> Report verdict: PASS, PASS_WITH_WARNINGS, or NEEDS_FIXES."
+**Prompt**:
+> {{AGENT_PROMPT_REVIEWER_REVIEW}}
 
 Wait for Reviewer to return.
 

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

@@ -1,18 +1,13 @@
 ### Review + Test — Reviewer Agent
 
-Spawn Reviewer agent (Agent tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false).
+**Spawn Agent**:
+| Parameter | Value |
+|-----------|-------|
+| subagent_type | prizm-dev-team-reviewer |
+| run_in_background | false |
 
-Prompt:
-> "Read {{REVIEWER_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
-> **IMPORTANT**: Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST.
-> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`:
->    - Section 3: Prizm Context (RULES, PATTERNS to check against)
->    - Section 4: File Manifest (original file structure)
->    - '## Implementation Log': what Dev changed, key decisions, discoveries
-> 2. Run prizmkit-code-review (both phases): Phase 1 diagnostic review (spec compliance, code quality, correctness), then Phase 2 fix strategy formulation for any findings. Read ONLY files listed in Implementation Log for diagnosis; MAY read additional files for impact analysis.
-> 3. Run the full test suite using `TEST_CMD=<TEST_CMD>` — **ONLY if the Implementation Log does not already confirm all tests passing**. If Implementation Log states tests passed, trust it and skip the re-run. When running tests: `$TEST_CMD 2>&1 | tee /tmp/review-test-out.txt | tail -20`, then grep `/tmp/review-test-out.txt` for details — do NOT re-run the suite multiple times. Write and execute integration tests covering all user stories from spec.md.
-> 4. Write structured '## Review Notes' to context-snapshot.md with Fix Instructions (Root Cause, Impact, Fix Strategy, Code Guidance, Verification for each finding) and Re-Review Expectations.
-> Report verdict: PASS, PASS_WITH_WARNINGS, or NEEDS_FIXES."
+**Prompt**:
+> {{AGENT_PROMPT_REVIEWER_REVIEW}}
 
 Wait for Reviewer to return.
 
@@ -24,13 +19,7 @@ grep -q "## Review Notes" .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md &
 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 NEEDS_FIXES: spawn Dev to fix with this prompt:
-  > "Read {{DEV_SUBAGENT_PATH}}. Fix NEEDS_FIXES issues for feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}).
-  > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` — '## Review Notes' section contains structured Fix Instructions with exact steps.
-  > 2. Follow Fix Instructions in order (respect Depends On / Blocks dependencies). Each FIX-N has: Root Cause, Fix Strategy, Code Guidance, and Verification criteria.
-  > 3. After each fix, run the Verification command listed in that FIX-N to confirm it works.
-  > 4. Use `TEST_CMD=<TEST_CMD>` to verify no regressions.
-  > 5. Append fix summary to '## Implementation Log' in context-snapshot.md.
-  > 6. Do NOT execute any git commands."
+  > {{AGENT_PROMPT_DEV_FIX}}
   Then re-run Review (max 3 rounds).
 
 **CP-3**: Integration tests pass, verdict is not NEEDS_FIXES.

package/bundled/dev-pipeline/templates/sections/test-failure-recovery.md

@@ -0,0 +1,75 @@
+## Test Failure Recovery Protocol
+
+When tests fail during implementation (Phase 3 / Phase 4):
+
+### Immediate Action — Recovery Attempt (Max 2 Rounds)
+
+1. **Analyze failure output**:
+   - Read the test failure message carefully
+   - Identify: root cause (code bug vs. test brittleness vs. environment issue)
+   - Check if baseline already recorded this failure (in BASELINE_FAILURES)
+
+2. **Categorize failure**:
+   - **Pre-existing baseline failure** (expected): Record as acceptable, do NOT fix
+   - **New regression**: Code introduced a bug, fix the code
+   - **Brittle test**: Test passes/fails inconsistently, fix the test or environment
+   - **Environment issue**: Missing dependency, wrong config, fix setup
+
+3. **Fix and re-run** (first round):
+   - Apply fix (code or test, not environment)
+   - Re-run `$TEST_CMD` to verify
+   - If now passing → continue to next task
+   - If still failing → **proceed to Round 2**
+
+4. **Second fix attempt** (second round only):
+   - Re-analyze the failure with fresh perspective
+   - Try alternate fix approach
+   - Re-run `$TEST_CMD`
+   - If still failing after Round 2 → **escalate** (see below)
+
+### Escalation Paths
+
+**Tier 1 (Single Agent)**:
+- After max 2 fix rounds with tests still failing
+- Document failure in Implementation Log with root cause analysis
+- Attempt one manual fix by re-reading related source code
+- If unable to resolve: record PARTIAL status with known failure list
+- **Do NOT block commit**; tests can fail during development (recovery may be deferred to next session)
+
+**Tier 2/3 (Dev + Reviewer)**:
+- After Dev completes max 2 fix rounds with tests still failing
+- Dev appends failure details to Implementation Log
+- Reviewer agent runs full test suite in Phase 5
+- If Reviewer confirms NEW regressions (not in baseline): mark verdict as `NEEDS_FIXES`
+- If Reviewer confirms only baseline failures remain: proceed with `PASS_WITH_WARNINGS`
+
+### Context-Aware Test Re-run (Performance Optimization)
+
+**Skip redundant re-runs**:
+- If Implementation Log section in context-snapshot.md already confirms "all tests passing"
+- → Skip Phase 5 test suite re-run (Reviewer will verify baseline log instead)
+- This avoids rebuilding/re-running tests when already verified
+
+**When to re-run**:
+- If Implementation Log is missing or incomplete
+- If any new code was added after the last test run
+- If Reviewer suspects brittleness or environment drift
+
+### Failure Capture Rules
+
+If tests remain broken after recovery:
+
+```
+## Test Failures Encountered
+
+- **Test**: [test name/path]
+  - Root Cause: [explanation]
+  - Category: [pre-existing baseline | new regression | brittle test | environment]
+  - Fix Attempted: [describe what was tried]
+  - Status: [still failing | requires next session | known limitation]
+
+- **Impact on Feature**: [can AC be verified despite failure | blocks AC verification]
+```
+
+**Rule**: If any AC cannot be verified due to test failure, the feature is incomplete. Document in failure-log.md for next session.
+

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.0",
+  "version": "1.1.3",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",
@@ -72,7 +72,7 @@
       "hasScripts": false
     },
     "feature-workflow": {
-      "description": "One-stop entry point for feature development. Orchestrates app-planner → dev-pipeline-launcher → background execution. Handles multi-feature batch development from a single request.",
+      "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",
       "category": "orchestration-skill",
       "subcategory": "workflows",
@@ -80,8 +80,8 @@
       "hasScripts": false
     },
     "refactor-workflow": {
-      "description": "End-to-end refactor workflow: analyze → plan → implement → review → commit. Behavior-preserving.",
-      "tier": "1",
+      "description": "One-stop entry point for code refactoring. Orchestrates refactor-planner → refactor-pipeline-launcher → execution.",
+      "tier": "companion",
       "category": "orchestration-skill",
       "subcategory": "workflows",
       "hasAssets": false,
@@ -96,6 +96,14 @@
       "hasScripts": false
     },
     "app-planner": {
+      "description": "Plan a new application from scratch — vision, tech stack, feature decomposition, and validated feature-list.json.",
+      "tier": "companion",
+      "category": "orchestration-skill",
+      "subcategory": "pipelines",
+      "hasAssets": true,
+      "hasScripts": true
+    },
+    "feature-planner": {
       "description": "Interactive planning for new apps and incremental features; outputs validated feature-list.json for dev-pipeline.",
       "tier": "companion",
       "category": "orchestration-skill",
@@ -103,7 +111,7 @@
       "hasAssets": true,
       "hasScripts": true
     },
-    "dev-pipeline-launcher": {
+    "feature-pipeline-launcher": {
       "description": "Launch and manage the dev-pipeline from within an AI CLI session. Start pipeline in background, monitor logs, check status, stop pipeline.",
       "tier": "companion",
       "category": "orchestration-skill",
@@ -119,6 +127,22 @@
       "hasAssets": false,
       "hasScripts": false
     },
+    "refactor-planner": {
+      "description": "Interactive refactoring planner. Analyzes code structure and produces validated refactor-list.json for dev-pipeline execution.",
+      "tier": "companion",
+      "category": "orchestration-skill",
+      "subcategory": "pipelines",
+      "hasAssets": true,
+      "hasScripts": true
+    },
+    "refactor-pipeline-launcher": {
+      "description": "Launch and manage the refactor pipeline from within an AI CLI session.",
+      "tier": "companion",
+      "category": "orchestration-skill",
+      "subcategory": "pipelines",
+      "hasAssets": false,
+      "hasScripts": false
+    },
     "bug-fix-workflow": {
       "description": "Interactive single-bug fix in current session. Guides triage → reproduce → fix → review → commit without background pipeline.",
       "tier": "companion",
@@ -153,9 +177,12 @@
         "feature-workflow",
         "refactor-workflow",
         "app-planner",
+        "feature-planner",
         "bug-planner",
-        "dev-pipeline-launcher",
+        "feature-pipeline-launcher",
         "bugfix-pipeline-launcher",
+        "refactor-planner",
+        "refactor-pipeline-launcher",
         "bug-fix-workflow",
         "recovery-workflow"
       ]