prizmkit 1.0.153 → 1.1.1

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

@@ -0,0 +1,17 @@
+### Plan & Tasks
+
+```bash
+ls .prizmkit/specs/{{FEATURE_SLUG}}/plan.md 2>/dev/null
+```
+
+If missing, write it yourself:
+- `plan.md`: architecture — components, interfaces, data flow, files to create/modify, testing approach, and a Tasks section with `[ ]` checkboxes ordered by dependency
+
+**Database Design Gate** (if feature involves data persistence — new tables, schema changes, new entities):
+Before proceeding past CP-1, verify:
+1. Plan.md Data Model section references existing schema/model files (scan for `*.prisma`, `*.sql`, `migrations/`, `models/`, `*.entity.*` files; read them if not already in context-snapshot)
+2. All new tables/fields follow existing naming conventions, ID strategy, timestamp patterns, and constraint style
+3. No `[NEEDS CLARIFICATION]` remains in Data Model section — resolve by reading existing code and making a conservative choice that matches existing patterns. Document the resolution in plan.md.
+4. If a DB design decision genuinely cannot be resolved from existing code alone, document the assumption made and flag it in the Implementation Log for user review.
+
+**CP-1**: plan.md exists with Tasks section.

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

@@ -0,0 +1,16 @@
+### Plan & Tasks
+
+```bash
+ls .prizmkit/specs/{{FEATURE_SLUG}}/ 2>/dev/null
+```
+
+If plan.md missing, write it directly:
+- `plan.md`: key components, data flow, files to create/modify, and a Tasks section with `[ ]` checkboxes (each task = one implementable unit). Keep under 80 lines.
+
+**Database Design Gate** (if feature involves data persistence — new tables, schema changes, new entities):
+Before proceeding past CP-1:
+1. Scan for existing schema files (`*.prisma`, `*.sql`, `migrations/`, `models/`, `*.entity.*`) and read them
+2. Ensure new tables/fields follow existing naming conventions and constraint patterns
+3. Resolve all uncertain DB design decisions before writing Tasks — document choices in plan.md
+
+**CP-1**: plan.md exists with Tasks section.

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

@@ -0,0 +1,28 @@
+### Review + Test — Reviewer Subagent
+
+Spawn Reviewer subagent (Agent tool, 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."
+
+Wait for Reviewer to return.
+
+**Gate Check — Review Notes**:
+After Reviewer agent returns, verify the Review Notes were written:
+```bash
+grep -q "## Review Notes" .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.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 NEEDS_FIXES: spawn Dev to fix (Dev reads Fix Instructions in snapshot), re-run Review (max 3 rounds)
+
+**CP-3**: Tests pass, verdict is not NEEDS_FIXES.

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

@@ -0,0 +1,36 @@
+### Review + Test — 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}}):
+> **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."
+
+Wait for Reviewer to return.
+
+**Gate Check — Review Notes**:
+After Reviewer agent returns, verify the Review Notes were written:
+```bash
+grep -q "## Review Notes" .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.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 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."
+  Then re-run Review (max 3 rounds).
+
+**CP-3**: Integration tests pass, verdict is not NEEDS_FIXES.

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

@@ -0,0 +1,82 @@
+### Specify + Plan (Full Workflow)
+
+**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 Phase 6 retrospective
+- Do NOT delete failure-log.md until this session completes all phases and commits successfully
+
+Check existing artifacts first:
+```bash
+ls .prizmkit/specs/{{FEATURE_SLUG}}/ 2>/dev/null
+```
+
+- Both (spec.md, plan.md) exist → **SKIP to CP-1**
+- `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 (search in source directories identified from `root.prizm` or the project tree scan):
+```bash
+grep -r "{{FEATURE_SLUG}}" . --include="*.js" --include="*.ts" --include="*.py" --include="*.go" --include="*.java" --include="*.rb" --include="*.rs" -l --exclude-dir=node_modules --exclude-dir=.git --exclude-dir=dist --exclude-dir=build --exclude-dir=vendor --exclude-dir=.prizmkit 2>/dev/null | head -20
+```
+
+Record result as `EXISTING_CODE` (list of files, or empty).
+
+If `EXISTING_CODE` is non-empty: your spec/plan/tasks must reflect this existing implementation — document what exists, identify gaps, do NOT re-implement what is already done.
+
+**Step A — Build Context Snapshot** (skip if `context-snapshot.md` already exists):
+
+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'
+     ```
+   - **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>
+   - **Section 5 — Existing Tests**: full content of related test files as code blocks
+5. Confirm: `ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`
+
+**After Step A**: Use context-snapshot.md Section 4 File Manifest to guide targeted file reads. Do NOT scan directories or read unrelated files.
+
+**Step B — Planning Artifacts** (generate only missing files):
+
+```bash
+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)
+
+> All files go under `.prizmkit/specs/{{FEATURE_SLUG}}/`. Confirm each with `ls` after writing.
+
+**Database Design Gate** (if feature involves data persistence — new tables, schema changes, new entities):
+Before proceeding past CP-1, verify:
+1. Plan.md Data Model section references existing schema/model files (scan for `*.prisma`, `*.sql`, `migrations/`, `models/`, `*.entity.*` files; read them if not already in context-snapshot)
+2. All new tables/fields follow existing naming conventions, ID strategy, timestamp patterns, and constraint style
+3. No `[NEEDS CLARIFICATION]` remains in Data Model section — resolve by reading existing code and making a conservative choice that matches existing patterns. Document the resolution in plan.md.
+4. If a DB design decision genuinely cannot be resolved from existing code alone, document the assumption made and flag it in the Implementation Log for user review.
+
+**CP-1**: Both spec.md and plan.md exist.

package/bundled/dev-pipeline/templates/sections/phase0-init.md

@@ -0,0 +1,4 @@
+### Phase 0: Project Bootstrap
+- Run `/prizmkit-init` (invoke the prizmkit-init skill)
+- Run `python3 {{INIT_SCRIPT_PATH}} --project-root {{PROJECT_ROOT}} --feature-id {{FEATURE_ID}} --feature-slug {{FEATURE_SLUG}}`
+- **CP-0**: Verify `.prizm-docs/root.prizm`, `.prizmkit/config.json` exist

package/bundled/dev-pipeline/templates/sections/phase0-test-baseline.md

@@ -0,0 +1,12 @@
+### Phase 0: Record Test Baseline & Detect Test Commands
+
+**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.

package/bundled/dev-pipeline/templates/sections/resume-header.md

@@ -0,0 +1,2 @@
+### Resume from Phase {{RESUME_PHASE}}
+Check `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` — if it exists, skip context building and use it directly.

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

@@ -0,0 +1,6 @@
+## Session Context
+
+- **Feature ID**: {{FEATURE_ID}} | **Session**: {{SESSION_ID}} | **Run**: {{RUN_ID}}
+- **Complexity**: {{COMPLEXITY}} | **Retry**: {{RETRY_COUNT}} / {{MAX_RETRIES}}
+- **Previous Status**: {{PREV_SESSION_STATUS}} | **Resume From**: {{RESUME_PHASE}}
+- **Init**: {{INIT_DONE}} | Artifacts: spec={{HAS_SPEC}} plan={{HAS_PLAN}}

package/bundled/dev-pipeline/templates/sections/subagent-timeout-recovery.md

@@ -0,0 +1,6 @@
+## Subagent Timeout Recovery
+
+If any agent times out:
+1. `ls .prizmkit/specs/{{FEATURE_SLUG}}/` — check what exists
+2. If `context-snapshot.md` exists: open recovery prompt with `"Read .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md for project context and any Implementation Log/Review Notes from previous agents. Run git diff HEAD to see actual code changes already made. Do NOT re-read individual source files unless the File Manifest directs you to."` + only remaining steps + `model: "lite"`
+3. Max 2 retries per phase. After 2 failures, orchestrator completes the work directly and appends a Recovery Note to context-snapshot.md.

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.153",
+  "version": "1.1.1",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",
@@ -15,22 +15,8 @@
       "hasAssets": false,
       "hasScripts": false
     },
-    "prizmkit-specify": {
-      "description": "Create structured feature specifications from natural language.",
-      "tier": "1",
-      "category": "prizmkit-skill",
-      "hasAssets": true,
-      "hasScripts": false
-    },
-    "prizmkit-clarify": {
-      "description": "Interactive requirement clarification. Resolves ambiguities in feature specs. Use when spec has unclear parts or you're unsure about requirements before planning.",
-      "tier": "1",
-      "category": "prizmkit-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
     "prizmkit-plan": {
-      "description": "Generate technical implementation plan and executable task breakdown from feature spec.",
+      "description": "Specify and plan features: natural language → spec.md → plan.md with architecture and executable tasks.",
       "tier": "1",
       "category": "prizmkit-skill",
       "hasAssets": true,
@@ -85,174 +71,78 @@
       "hasAssets": true,
       "hasScripts": false
     },
-    "prizmkit-tool-tech-debt-tracker": {
-      "description": "Identify and track technical debt via code pattern analysis.",
-      "tier": "1",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-bug-reproducer": {
-      "description": "Generate minimal reproduction scripts and test cases from bug descriptions.",
-      "tier": "1",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-adr-manager": {
-      "description": "Manage Architecture Decision Records. Create, list, and supersede ADRs.",
-      "tier": "1",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": true,
-      "hasScripts": false
-    },
-    "prizmkit-tool-security-audit": {
-      "description": "AI-assisted security review checklist via static code analysis.",
-      "tier": "2",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-dependency-health": {
-      "description": "Dependency review based on manifest files.",
-      "tier": "2",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-ci-cd-generator": {
-      "description": "Generate CI/CD pipeline config templates for GitHub Actions/GitLab CI/Jenkins.",
-      "tier": "2",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-deployment-strategy": {
-      "description": "Deployment planning with rollback procedures.",
-      "tier": "2",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-db-migration": {
-      "description": "Database migration script generation with rollback plans.",
-      "tier": "2",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-monitoring-setup": {
-      "description": "Generate monitoring config templates for Prometheus/Grafana/CloudWatch.",
-      "tier": "2",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-error-triage": {
-      "description": "Error categorization and root cause analysis via pattern matching.",
-      "tier": "2",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-log-analyzer": {
-      "description": "Log pattern recognition via text analysis.",
-      "tier": "2",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-perf-profiler": {
-      "description": "Static analysis for potential performance issues.",
-      "tier": "2",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-onboarding-generator": {
-      "description": "Generate onboarding documentation from Prizm docs context.",
-      "tier": "2",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "hasScripts": false
-    },
-    "prizmkit-tool-api-doc-generator": {
-      "description": "Extract API documentation from source code into OpenAPI/Markdown.",
-      "tier": "2",
-      "category": "prizmkit-tool-skill",
-      "hasAssets": false,
-      "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.",
       "tier": "companion",
-      "category": "Custom-skill",
+      "category": "orchestration-skill",
+      "subcategory": "workflows",
       "hasAssets": false,
       "hasScripts": false
     },
     "refactor-workflow": {
       "description": "End-to-end refactor workflow: analyze → plan → implement → review → commit. Behavior-preserving.",
       "tier": "1",
-      "category": "Custom-skill",
+      "category": "orchestration-skill",
+      "subcategory": "workflows",
       "hasAssets": false,
       "hasScripts": false
     },
     "bug-planner": {
       "description": "Interactive bug planning that produces bug-fix-list.json. Supports stack traces, user reports, failed tests, log patterns, monitoring alerts.",
       "tier": "companion",
-      "category": "Custom-skill",
+      "category": "orchestration-skill",
+      "subcategory": "pipelines",
       "hasAssets": false,
       "hasScripts": false
     },
     "app-planner": {
       "description": "Interactive planning for new apps and incremental features; outputs validated feature-list.json for dev-pipeline.",
       "tier": "companion",
-      "category": "Custom-skill",
+      "category": "orchestration-skill",
+      "subcategory": "pipelines",
       "hasAssets": true,
       "hasScripts": true
     },
     "dev-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": "Custom-skill",
+      "category": "orchestration-skill",
+      "subcategory": "pipelines",
       "hasAssets": false,
       "hasScripts": false
     },
     "bugfix-pipeline-launcher": {
       "description": "Launch and manage the bugfix pipeline from within a CLI session.",
       "tier": "companion",
-      "category": "Custom-skill",
+      "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",
-      "category": "Custom-skill",
+      "category": "orchestration-skill",
+      "subcategory": "workflows",
       "hasAssets": false,
       "hasScripts": false
     },
     "recovery-workflow": {
       "description": "Recover and resume interrupted feature pipeline sessions. Detects partial work from failed or interrupted sessions and resumes from the correct phase.",
       "tier": "companion",
-      "category": "Custom-skill",
+      "category": "orchestration-skill",
+      "subcategory": "workflows",
       "hasAssets": false,
       "hasScripts": false
     }
   },
   "suites": {
-    "full": {
-      "description": "All skills",
-      "skills": "*"
-    },
     "core": {
-      "description": "Core workflow: minimal closed-loop + all orchestration and planning skills (Custom-skill)",
+      "description": "All skills: full spec-driven cycle + orchestration + planning + recovery",
       "skills": [
         "prizm-kit",
         "prizmkit-init",
         "prizmkit-prizm-docs",
-        "prizmkit-specify",
-        "prizmkit-clarify",
         "prizmkit-plan",
         "prizmkit-analyze",
         "prizmkit-implement",
@@ -266,7 +156,8 @@
         "bug-planner",
         "dev-pipeline-launcher",
         "bugfix-pipeline-launcher",
-        "bug-fix-workflow"
+        "bug-fix-workflow",
+        "recovery-workflow"
       ]
     },
     "minimal": {
@@ -275,8 +166,6 @@
         "prizm-kit",
         "prizmkit-init",
         "prizmkit-prizm-docs",
-        "prizmkit-specify",
-        "prizmkit-clarify",
         "prizmkit-plan",
         "prizmkit-analyze",
         "prizmkit-implement",
@@ -286,51 +175,6 @@
       ]
     }
   },
-  "recommendations": {
-    "frontend": {
-      "label": "Frontend (React/Vue/Angular)",
-      "base": "core",
-      "include": [
-        "prizmkit-tool-perf-profiler",
-        "prizmkit-tool-security-audit",
-        "prizmkit-tool-ci-cd-generator"
-      ]
-    },
-    "backend": {
-      "label": "Backend (API/Microservices)",
-      "base": "core",
-      "include": [
-        "prizmkit-tool-db-migration",
-        "prizmkit-tool-api-doc-generator",
-        "prizmkit-tool-monitoring-setup",
-        "prizmkit-tool-deployment-strategy",
-        "prizmkit-tool-security-audit",
-        "prizmkit-tool-error-triage",
-        "prizmkit-tool-log-analyzer"
-      ]
-    },
-    "fullstack": {
-      "label": "Full-Stack",
-      "base": "core",
-      "include": [
-        "prizmkit-tool-db-migration",
-        "prizmkit-tool-api-doc-generator",
-        "prizmkit-tool-ci-cd-generator",
-        "prizmkit-tool-security-audit",
-        "prizmkit-tool-deployment-strategy",
-        "prizmkit-tool-perf-profiler"
-      ]
-    },
-    "library": {
-      "label": "Library/SDK",
-      "base": "core",
-      "include": [
-        "prizmkit-tool-api-doc-generator",
-        "prizmkit-tool-ci-cd-generator",
-        "prizmkit-tool-dependency-health"
-      ]
-    }
-  },
   "external_skills": {
     "known": [
       {

package/bundled/skills/app-planner/SKILL.md

@@ -38,6 +38,7 @@ The user chose this skill intentionally. Respect that choice.
 2. Architecture decisions appended to `CLAUDE.md` / `CODEBUDDY.md` (with user consent, see §Architecture Decision Capture)
 3. Draft backups in `.prizmkit/planning/`
 4. `.prizmkit/project-conventions.json` (project convention answers, see §Project Conventions Check)
+5. `project-brief.md` (project root — accumulated project context brief for headless pipeline sessions)
 
 **After planning is complete**, you MUST:
 1. Present the summary and recommended next step
@@ -92,13 +93,18 @@ Do NOT use this skill when the user only wants to run the pipeline (`dev-pipelin
    → If all conventions are already answered → skip silently, do not re-ask
    → Use convention answers as context when writing feature descriptions and proposing features (see `${SKILL_DIR}/references/project-conventions.md` §How Conventions Are Used)
 
-7. **Always validate output via script**:
+7. **Project brief accumulation** — Throughout all interactive phases, accumulate a `project-brief.md` at project root:
+   → Read `${SKILL_DIR}/references/project-brief-guide.md` for the file template, trigger rules, and update rules
+   → Update after each meaningful user response containing business intent, constraints, design decisions, or emphasized details
+   → Verify at CP-AP-5.3 before generating `feature-list.json`
+
+8. **Always validate output via script**:
    - run:
      ```bash
      python3 ${SKILL_DIR}/scripts/validate-and-generate.py validate --input <output-path> --mode <new|incremental>
      ```
 
-8. **Use script output as source of truth**:
+9. **Use script output as source of truth**:
    - if validation fails, **MUST** fix and re-run until pass
 
 ## Prerequisites
@@ -173,7 +179,7 @@ Execute the selected scenario workflow in conversation mode with mandatory check
 ### Interactive Phases
 1. clarify business goal and scope
    1.1 confirm deliverable intent (→ Intent Confirmation)
-   1.2 **requirement clarification** — apply `/prizmkit-clarify` principles: for ANY unclear aspect of the user's vision, goals, target users, or scope, ask questions one at a time until you fully understand. No limit on rounds or number of questions. Do not proceed to Phase 2 with unresolved ambiguities.
+   1.2 **requirement clarification** — for ANY unclear aspect of the user's vision, goals, target users, or scope, ask questions one at a time (cite the unclear point, give a recommended answer with rationale) until you fully understand. No limit on rounds or number of questions. Do not proceed to Phase 2 with unresolved ambiguities.
 2. confirm constraints and tech assumptions
 3. propose feature set with dependencies
 4. refine descriptions and acceptance criteria
@@ -201,6 +207,7 @@ Note: Checkpoint numbers (CP-AP-N) are sequential identifiers for the gate, NOT
 | **CP-AP-5** | DAG Validity | No cycles, dependencies resolved (validation dry-run) | 5 |
 | **CP-AP-5.1** | Browser Interaction Applied | Qualifying features have `browser_interaction` field; user confirmed or opted out | 4 |
 | **CP-AP-5.2** | Testing Defaults Applied | All features have appropriate `critic`, `critic_count`, and testing expectations per §Testing Defaults | 7 |
+| **CP-AP-5.3** | Project Brief Accumulated | `project-brief.md` exists at project root with Vision + at least one other section | 5 |
 | **CP-AP-6** | `feature-list.json` Generated | Schema validates, all required keys present | 6-7 |
 | **CP-AP-7** | Final Validation Pass | Python script returns `"valid": true` with zero errors | 8 |
 
@@ -377,6 +384,18 @@ Key behaviors:
 - Interrupted session → detect checkpoint from existing artifacts, offer resume or restart
 - `feature-list.json` MUST be written to project root (same level as `package.json` / `.git`)
 
+## Project Brief Accumulation
+
+During interactive planning, maintain a `project-brief.md` at the project root that distills the user's key requirements, design decisions, and context for headless pipeline sessions.
+
+→ Read `${SKILL_DIR}/references/project-brief-guide.md` for the file template, accumulation trigger, update rules, and examples.
+
+**Key rules** (full details in guide):
+- Update after each meaningful user response that contains business intent, constraints, design decisions, or emphasized details
+- Fixed 4-section structure: Vision, Core Constraints, Design Decisions, Key Requirements
+- Max 500 words; one sentence per bullet
+- Checkpoint **CP-AP-5.3**: must exist with Vision + at least one other populated section before CP-AP-6
+
 ## Session Exit Gate
 
 Prevent accidental session exit without deliverable completion.