prizmkit 1.1.25 → 1.1.26

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.25",
-  "bundledAt": "2026-04-12T02:12:31.973Z",
-  "bundledFrom": "b63b063"
+  "frameworkVersion": "1.1.26",
+  "bundledAt": "2026-04-12T02:27:49.522Z",
+  "bundledFrom": "c191f35"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.25",
+  "version": "1.1.26",
   "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/bug-fix-workflow/SKILL.md

@@ -164,15 +164,15 @@ AskUserQuestion:
   header: "Approach"
   options:
     - label: "Fix now (fast path)"
-      description: "Implement the fix directly in this session"
-    - label: "Add to bug list"
-      description: "Add to .prizmkit/plans/bug-fix-list.json for pipeline execution later"
+      description: "Implement the fix directly in this session — branch → test → fix → review → commit"
+    - label: "Add to bug-fix-list.json (pipeline)"
+      description: "Add this bug to .prizmkit/plans/bug-fix-list.json via bug-planner, then use bugfix-pipeline-launcher to launch autonomous pipeline execution"
     - label: "Full diagnosis"
       description: "Continue with in-depth analysis before deciding"
 ```
 
 - **Fix now** → Proceed with Fast Path Workflow (Phase 0 branch already set up)
-- **Add to bug list** → Invoke `bug-planner` to add this bug to the list, then end this workflow
+- **Add to bug-fix-list.json** → Invoke `bug-planner` to add this bug to `.prizmkit/plans/bug-fix-list.json`, then suggest user run `bugfix-pipeline-launcher` to start the pipeline. End this workflow.
 - **Full diagnosis** → Continue with full diagnosis (Phase 2 Triage)
 
 **Complex bug → Planning Path** (ANY is true):
@@ -191,15 +191,15 @@ AskUserQuestion:
   options:
     - label: "Plan and fix now"
       description: "Create a plan and fix it in this session using /prizmkit-plan + /prizmkit-implement"
-    - label: "Add to bug list"
-      description: "Add to .prizmkit/plans/bug-fix-list.json for pipeline execution later"
+    - label: "Add to bug-fix-list.json (pipeline)"
+      description: "Add this bug to .prizmkit/plans/bug-fix-list.json via bug-planner, then use bugfix-pipeline-launcher to launch autonomous pipeline execution"
 ```
 
 - **Plan and fix now** → Invoke `/prizmkit-plan` with `artifact_dir=.prizmkit/bugfix/<BUG_ID>/`:
   1. prizmkit-plan generates `spec.md` + `plan.md` under `.prizmkit/bugfix/<BUG_ID>/`
   2. Invoke `/prizmkit-implement` to execute the plan
   3. After implementation, resume this workflow at Phase 5 (Review)
-- **Add to bug list** → Invoke `bug-planner` to add this bug to the list, then end this workflow
+- **Add to bug-fix-list.json** → Invoke `bug-planner` to add this bug to `.prizmkit/plans/bug-fix-list.json`, then suggest user run `bugfix-pipeline-launcher` to start the pipeline. End this workflow.
 
 **NEVER proceed with direct code changes without explicit user confirmation via `AskUserQuestion`. Do NOT render options as plain text — the user must be able to click/select.**
 

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

@@ -250,12 +250,75 @@ Once brainstorming is complete, produce a structured requirements summary:
 ### Confirmed by user: ✓
 ```
 
-Present this summary to the user and get explicit confirmation before proceeding to Phase 2.
+Present this summary to the user and get explicit confirmation before proceeding.
 
 **CHECKPOINT CP-FW-0**: Requirements fully clarified and confirmed by user.
 
 ---
 
+### Step 1.7: Complexity Assessment & Approach Selection
+
+After confirming requirements, assess whether this feature needs the full pipeline or can be done directly in the current session.
+
+**Simple feature → Fast Path candidate** (ALL must be true):
+- Single module, no cross-module architectural impact
+- ≤2 new files to create
+- No new external dependencies or infrastructure changes
+- Straightforward implementation (CRUD, utility, simple UI component)
+- Clear acceptance criteria with existing patterns to follow
+- No dependency on other unbuilt features
+
+**User choice required (mandatory)** — Use `AskUserQuestion` to present interactive selectable options:
+
+```
+AskUserQuestion:
+  question: "This feature appears straightforward. How would you like to proceed?"
+  header: "Approach"
+  options:
+    - label: "Implement now (fast path)"
+      description: "Plan and implement directly in this session using /prizmkit-plan + /prizmkit-implement"
+    - label: "Add to feature list (pipeline)"
+      description: "Generate .prizmkit/plans/feature-list.json via feature-planner, then launch pipeline for autonomous execution"
+```
+
+- **Implement now** → Fast Path Workflow:
+  1. Invoke `/prizmkit-plan` with the requirements summary → generates `spec.md` + `plan.md`
+  2. Invoke `/prizmkit-implement` to execute the plan
+  3. After implementation, run `/prizmkit-code-review` for quality check
+  4. Commit via `/prizmkit-committer` with `feat(<scope>):` prefix
+  5. Run `/prizmkit-retrospective` to sync `.prizm-docs/`
+  6. **End workflow** — skip Phase 2/3/4
+- **Add to feature list** → Continue to Phase 2 (Plan via pipeline)
+
+**Complex feature → Planning Path** (ANY is true):
+- Cross-module impact (>2 modules affected)
+- New infrastructure, dependencies, or architectural patterns required
+- Multiple interrelated features with dependency ordering
+- Data model or API design decisions needed
+- Requires integration with external services
+
+**User choice required (mandatory)** — Use `AskUserQuestion` to present interactive selectable options:
+
+```
+AskUserQuestion:
+  question: "This feature is complex and will benefit from structured planning. How would you like to proceed?"
+  header: "Approach"
+  options:
+    - label: "Plan and implement now"
+      description: "Create a plan and implement in this session using /prizmkit-plan + /prizmkit-implement"
+    - label: "Add to feature list (pipeline)"
+      description: "Generate .prizmkit/plans/feature-list.json via feature-planner, then launch pipeline for autonomous execution"
+```
+
+- **Plan and implement now** → Invoke `/prizmkit-plan` with requirements → `/prizmkit-implement` → `/prizmkit-code-review` → `/prizmkit-committer` → `/prizmkit-retrospective`. **End workflow** — skip Phase 2/3/4.
+- **Add to feature list** → Continue to Phase 2 (Plan via pipeline)
+
+**NEVER proceed without explicit user confirmation via `AskUserQuestion`. Do NOT render options as plain text — the user must be able to click/select.**
+
+**CHECKPOINT CP-FW-0.5**: Approach selected by user (fast path or pipeline).
+
+---
+
 ## Phase 2: Plan
 
 **Goal**: Generate structured .prizmkit/plans/feature-list.json from the clarified requirements.

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

@@ -251,12 +251,76 @@ Once brainstorming is complete, produce a structured goals summary:
 ### Confirmed by user: ✓
 ```
 
-Present this summary to the user and get explicit confirmation before proceeding to Phase 2.
+Present this summary to the user and get explicit confirmation before proceeding.
 
 **CHECKPOINT CP-RW-0**: Refactoring goals fully clarified and confirmed by user.
 
 ---
 
+### Step 1.7: Complexity Assessment & Approach Selection
+
+After confirming refactoring goals, assess whether this refactor needs the full pipeline or can be done directly in the current session.
+
+**Simple refactor → Fast Path candidate** (ALL must be true):
+- Single module, no cross-module impact
+- ≤3 files affected
+- No public API or interface changes
+- Straightforward transformation (extract method, rename, move file, simplify logic)
+- Existing tests fully cover the affected code paths
+- No risk of behavior change
+
+**User choice required (mandatory)** — Use `AskUserQuestion` to present interactive selectable options:
+
+```
+AskUserQuestion:
+  question: "This refactoring appears straightforward. How would you like to proceed?"
+  header: "Approach"
+  options:
+    - label: "Refactor now (fast path)"
+      description: "Plan and refactor directly in this session using /prizmkit-plan + /prizmkit-implement"
+    - label: "Add to refactor list (pipeline)"
+      description: "Generate .prizmkit/plans/refactor-list.json via refactor-planner, then launch pipeline for autonomous execution"
+```
+
+- **Refactor now** → Fast Path Workflow:
+  1. Invoke `/prizmkit-plan` with the refactoring goals → generates `spec.md` + `plan.md`
+  2. Invoke `/prizmkit-implement` to execute the plan (behavior preservation verified by tests)
+  3. After implementation, run `/prizmkit-code-review` for quality check
+  4. Commit via `/prizmkit-committer` with `refactor(<scope>):` prefix
+  5. Run `/prizmkit-retrospective` to sync `.prizm-docs/`
+  6. **End workflow** — skip Phase 2/3/4
+- **Add to refactor list** → Continue to Phase 2 (Plan via pipeline)
+
+**Complex refactor → Planning Path** (ANY is true):
+- Cross-module impact (>2 modules affected)
+- Public API or interface changes required
+- Multiple interrelated refactoring steps with dependency ordering
+- Comprehensive rewrite of a module
+- Insufficient test coverage in target area (risk of hidden behavior changes)
+- Requires coordination with other ongoing work
+
+**User choice required (mandatory)** — Use `AskUserQuestion` to present interactive selectable options:
+
+```
+AskUserQuestion:
+  question: "This refactoring is complex and will benefit from structured planning. How would you like to proceed?"
+  header: "Approach"
+  options:
+    - label: "Plan and refactor now"
+      description: "Create a plan and refactor in this session using /prizmkit-plan + /prizmkit-implement"
+    - label: "Add to refactor list (pipeline)"
+      description: "Generate .prizmkit/plans/refactor-list.json via refactor-planner, then launch pipeline for autonomous execution"
+```
+
+- **Plan and refactor now** → Invoke `/prizmkit-plan` with goals → `/prizmkit-implement` → `/prizmkit-code-review` → `/prizmkit-committer` → `/prizmkit-retrospective`. **End workflow** — skip Phase 2/3/4.
+- **Add to refactor list** → Continue to Phase 2 (Plan via pipeline)
+
+**NEVER proceed without explicit user confirmation via `AskUserQuestion`. Do NOT render options as plain text — the user must be able to click/select.**
+
+**CHECKPOINT CP-RW-0.5**: Approach selected by user (fast path or pipeline).
+
+---
+
 ## Phase 2: Plan
 
 **Goal**: Generate structured .prizmkit/plans/refactor-list.json from the clarified refactoring goals.

package/package.json

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