prizmkit 1.0.109 → 1.0.111

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.109",
-  "bundledAt": "2026-03-26T02:14:25.170Z",
-  "bundledFrom": "d4369e9"
+  "frameworkVersion": "1.0.111",
+  "bundledAt": "2026-03-26T05:28:57.400Z",
+  "bundledFrom": "dacaffd"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.109",
+  "version": "1.0.111",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",

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

@@ -14,10 +14,10 @@ Always produce a validated `feature-list.json` that conforms to `dev-pipeline-fe
 ## When to Use
 
 Trigger this skill for requests like:
-- "Plan an app", "Design a project", "Plan an app", "Design a new application"
-- "Add features to existing system", "Continue planning", "Add features", "Continue planning"
+- "Plan an app", "Design a project", "Design a new application"
+- "Add features to existing system", "Continue planning"
 - "Prepare feature-list.json", "Prepare dev-pipeline input"
-- "Reprioritize features", "Split features", "reprioritize/scope features"
+- "Reprioritize features", "Split features"
 
 Do NOT use this skill when:
 - user only wants to run pipeline now (invoke `dev-pipeline-launcher`)
@@ -130,6 +130,55 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
 
 **Resume Detection**: See §Resume Support for checkpoint-based resumption.
 
+## Architecture Decision Capture
+
+During planning, key **framework-level** architectural decisions may emerge. When they do, capture them in the project instruction file so all future AI sessions have this context.
+
+### What Qualifies (ALL must apply)
+
+Only capture decisions that are **framework-shaping** — NOT individual feature details. Qualifying categories:
+
+| Category | Examples |
+|----------|----------|
+| Tech stack choices | PostgreSQL over MongoDB, React over Vue, Node.js runtime |
+| Communication patterns | REST vs GraphQL, WebSocket vs SSE vs polling |
+| Architectural patterns | Monorepo, microservices, monolith, event-driven |
+| Data model strategies | Relational vs document, event sourcing, CQRS |
+| Security architecture | JWT vs session, OAuth provider, RBAC model |
+
+**Do NOT capture**: individual feature implementation details, UI component choices, specific API endpoint designs, or anything scoped to a single feature.
+
+**This is conditional** — most planning sessions will NOT produce architecture decisions. Only capture when genuinely impactful decisions are made during the discussion.
+
+### When to Capture
+
+After Phase 5 (DAG verification), before Phase 6 (JSON generation). At this point decisions are settled.
+
+### How to Capture
+
+1. **Detect platform** — determine which project instruction file to update:
+   - `.claude/` directory exists → append to `CLAUDE.md`
+   - `.codebuddy/` directory exists → append to `CODEBUDDY.md`
+   - Both exist → append to both
+   - Neither exists → skip (no project instruction file)
+
+2. **Check for existing section** — read the target file and look for `### Architecture Decisions` heading:
+   - If heading exists → append new entries below it (avoid duplicates with existing entries)
+   - If heading does not exist → create it at the end of the file
+
+3. **Format** — one line per decision, no feature IDs:
+   ```markdown
+   ### Architecture Decisions
+   - WebSocket for real-time: sub-second latency required for collaboration features
+   - PostgreSQL: relational data model with complex queries, ACID compliance needed
+   - Monorepo structure: shared types between frontend and backend
+   ```
+
+4. **User confirmation** — before writing, show the collected decisions and ask:
+   > "These architecture decisions were identified during planning. Record them to [CLAUDE.md / CODEBUDDY.md]? (Y/n)"
+
+   If user declines, skip without further prompting.
+
 ## Fast Path — Incremental Shortcuts
 
 For simple incremental planning, skip detailed Phase 2-3 analysis to accelerate delivery:
@@ -376,9 +425,10 @@ When the session appears to be ending (user says "thanks", "that's all", "bye",
 1. **Remind**: "You set out to produce `feature-list.json` but we haven't completed it yet."
 2. **Offer 3 options**:
    - **(a) Continue to completion** — resume from current phase
-   - **(b) Abandon** — confirm user explicitly wants to exit without output
-3. **If (b) Save draft**: Write the draft file and remind user: "This is a draft, not validated. Run `/app-planner` again to resume and finalize."
-4. **If (c) Abandon**: Accept without further prompting.
+   - **(b) Save draft & exit** — write current progress as draft, exit session
+   - **(c) Abandon** — exit without saving
+3. **If (b)**: Write the draft file and remind user: "This is a draft, not validated. Run `/app-planner` again to resume and finalize."
+4. **If (c)**: Accept without further prompting.
 
 
 ## Handoff Message Template

package/bundled/skills/bug-fix-workflow/SKILL.md

@@ -23,11 +23,16 @@ Fix a single bug interactively within the current AI CLI session. This is the in
 
 ## Input
 
-The bug can come from:
-- **A bug-fix-list.json entry**: "fix B-001" → read the entry from bug-fix-list.json
-- **A stack trace/error message**: user pastes error directly
-- **A description**: "the login page crashes when I click submit"
-- **A failed test**: "this test is failing: src/auth/__tests__/login.test.ts"
+**PRECONDITION:**
+
+| Input Source | Detection | Example |
+|---|---|---|
+| Bug-fix-list.json entry | User says "fix B-001" → read entry from `bug-fix-list.json` | `fix B-001` |
+| Stack trace / error message | User pastes error directly | `TypeError: Cannot read property...` |
+| Natural language description | User describes the problem | "login page crashes on submit" |
+| Failed test | User references a failing test file | `src/auth/__tests__/login.test.ts` |
+
+At least one input source must be provided. If none is clear, ask the user to describe the bug.
 
 ## Fast Path
 

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

@@ -1,7 +1,7 @@
 ---
 name: "bug-planner"
 tier: companion
-description: "Interactive bug planning that produces bug-fix-list.json for the Bug Fix Pipeline. Supports multiple input formats: error logs, stack traces, user reports, failed tests, monitoring alerts. Use this skill whenever the user has bugs to report, errors to parse, or test failures to organize. Trigger on: 'plan bug fixes', 'report bugs', 'I have some bugs', 'these tests are failing', 'here is an error log', 'parse these errors', 'fix bugs', 'generate bug list', 'plan bug fixes'. (project)"
+description: "Interactive bug planning that produces bug-fix-list.json for the Bug Fix Pipeline. Supports multiple input formats: error logs, stack traces, user reports, failed tests, monitoring alerts. Use this skill whenever the user has bugs to report, errors to parse, or test failures to organize. Trigger on: 'plan bug fixes', 'report bugs', 'I have some bugs', 'these tests are failing', 'here is an error log', 'parse these errors', 'generate bug list'. (project)"
 ---
 
 # Bug Planner
@@ -12,9 +12,8 @@ Interactive skill that collects bug information from various input formats and g
 
 User says:
 - "plan bug fixes", "report bugs", "create bug list"
-- "fix bugs", "generate bug list", "plan bug fixes"
-- "I have some bugs to fix", "these tests are failing"
-- "here's an error log", "parse these errors"
+- "generate bug list", "I have some bugs to fix"
+- "these tests are failing", "here's an error log", "parse these errors"
 - After receiving bug reports, error logs, or failed test output
 
 **Do NOT use when:**
@@ -28,7 +27,7 @@ This skill handles multiple operations. Determine the user's intent and execute
 
 | User Intent | Operation | Trigger Phrases |
 |---|---|---|
-| Plan bugs interactively | **Interactive Planning** | "plan bug fixes", "report bugs", "plan bug fixes" |
+| Plan bugs interactively | **Interactive Planning** | "plan bug fixes", "report bugs" |
 | Parse error logs into bugs | **From Log** | "parse this error log", "here's a stack trace", "parse these errors" |
 | Parse test failures into bugs | **From Tests** | "these tests are failing", "parse test output" |
 | Validate existing bug list | **Validate** | "validate bug list", "check bug-fix-list.json" |

package/bundled/skills/bugfix-pipeline-launcher/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: "bugfix-pipeline-launcher"
-description: "Launch and manage the bugfix pipeline from within an AI CLI session. Start pipeline in background, monitor logs, check status, stop pipeline. Use this skill whenever the user wants to start fixing bugs, run the bugfix pipeline, check bugfix progress, or stop the bugfix pipeline. Trigger on: 'start fixing bugs', 'run bugfix pipeline', 'bugfix status', 'stop bug fix', 'launch bug fix', 'start fixing bugs', 'fix progress', 'stop fixing'. (project)"
+description: "Launch and manage the bugfix pipeline from within an AI CLI session. Start pipeline in background, monitor logs, check status, stop pipeline. Use this skill whenever the user wants to start fixing bugs, run the bugfix pipeline, check bugfix progress, or stop the bugfix pipeline. Trigger on: 'start fixing bugs', 'run bugfix pipeline', 'bugfix status', 'stop bug fix', 'launch bug fix', 'fix progress', 'stop fixing'. (project)"
 ---
 
 # Bugfix-Pipeline Launcher
@@ -29,9 +29,7 @@ Use daemon mode (`launch-bugfix-daemon.sh`) only when:
 
 **Start bugfix pipeline** -- User says:
 - "start fixing bugs", "run bugfix pipeline", "launch bug fixes", "fix all bugs"
-- "start bug fix", "run bug fix", "execute bug list", "begin fixing"
-- "launch bug fix", "start fixing bugs", "run bug fix pipeline", "start fixing bugs"
-- "fix all bugs", "batch fix", "launch fix pipeline"
+- "start bug fix", "execute bug list", "begin fixing", "batch fix"
 - After bug-planner completes: "fix them", "start fixing"
 
 **Check status** -- User says:
@@ -39,12 +37,11 @@ Use daemon mode (`launch-bugfix-daemon.sh`) only when:
 - "fix progress", "bug fix status", "check fix progress", "how far along are the fixes"
 
 **Stop bugfix pipeline** -- User says:
-- "stop bug fix", "stop fixing", "halt bugfix", "pause bug fix"
-- "stop fixing", "pause bug fix", "stop fix pipeline"
+- "stop bug fix", "stop fixing", "halt bugfix", "pause bug fix", "stop fix pipeline"
 
 **Show logs** -- User says:
 - "bugfix logs", "show fix logs", "what's being fixed"
-- "view fix logs", "fix logs", "check fix status"
+- "view fix logs", "fix logs"
 
 **Do NOT use this skill when:**
 - User wants to plan/collect bugs (use `bug-planner` instead)

package/bundled/skills/dev-pipeline-launcher/SKILL.md

@@ -25,14 +25,13 @@ Use daemon mode (`launch-daemon.sh`) only when:
 **Start pipeline** -- User says:
 - "run pipeline", "start pipeline", "start building", "launch dev-pipeline"
 - "run the features", "execute feature list", "start implementing"
-- "launch pipeline", "start implementing", "run the pipeline", "start auto-development"
-- "implement next steps", "execute feature list", "start building"
+- "launch pipeline", "run the pipeline", "start auto-development"
 - After app-planner completes: "build it", "start developing from the feature list"
 - "run only F-001 to F-005", "run features F-001,F-003", "only build these features"
 
 **Check status** -- User says:
 - "pipeline status", "check pipeline", "how's it going", "progress"
-- "pipeline status", "check progress", "what's the current situation"
+- "check progress", "what's the current situation"
 
 **Stop pipeline** -- User says:
 - "stop pipeline", "kill pipeline", "halt", "pause"
@@ -40,11 +39,10 @@ Use daemon mode (`launch-daemon.sh`) only when:
 
 **Show logs** -- User says:
 - "show logs", "pipeline logs", "tail logs", "what's happening"
-- "view logs", "pipeline logs", "check the logs"
+- "view logs", "check the logs"
 
 **Retry single feature node** -- User says:
-- "retry F-003", "retry this feature", "retry this node"
-- "retry F-003", "retry this node", "re-run this feature"
+- "retry F-003", "retry this feature", "retry this node", "re-run this feature"
 
 **Do NOT use this skill when:**
 - User wants to plan features (use `app-planner` instead)
@@ -148,14 +146,13 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 5. **Ask user to confirm**: "Ready to launch the pipeline? It will process N features."
 
-6. **Launch**:
-   ```bash
-   dev-pipeline/launch-daemon.sh start feature-list.json
-   ```
-   If user specified environment overrides (e.g. timeout, retries, verbose):
-   ```bash
-   dev-pipeline/launch-daemon.sh start feature-list.json --env "SESSION_TIMEOUT=7200 MAX_RETRIES=5"
-   ```
+6. **Launch** (based on chosen mode from step 4):
+   - Foreground: `dev-pipeline/run.sh run feature-list.json`
+   - Background: `dev-pipeline/launch-daemon.sh start feature-list.json`
+   - If user specified environment overrides:
+     ```bash
+     dev-pipeline/launch-daemon.sh start feature-list.json --env "SESSION_TIMEOUT=7200 MAX_RETRIES=5"
+     ```
 
 7. **Verify launch**:
    ```bash

package/bundled/skills/refactor-workflow/SKILL.md

@@ -56,6 +56,14 @@ Refactor artifacts stored at `.prizmkit/refactor/<refactor-slug>/`:
 - **`refactor-analysis.md`** — Code analysis (Phase 1)
 - **`plan.md`** — Refactoring plan with Tasks section (Phase 2)
 
+**PRECONDITION:**
+
+| Required | Check | If Missing |
+|---|---|---|
+| Refactoring target (module path, file path, or natural language description) | User provides target in request | Ask: "What module or code do you want to refactor?" |
+| Test suite exists for target module | Tests can be located and run | WARN user, recommend writing tests first before refactoring |
+| No uncommitted changes on current branch | `git status` is clean | Ask user to commit or stash changes first |
+
 **INPUT**: Target description. Can be:
 - Module or file path (e.g., "src/auth/")
 - Natural language description (e.g., "refactor the auth module, extract shared logic")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.0.109",
+  "version": "1.0.111",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {