prizmkit 1.1.24 → 1.1.26

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.24",
-  "bundledAt": "2026-04-12T01:13:39.954Z",
-  "bundledFrom": "626fbf5"
+  "frameworkVersion": "1.1.26",
+  "bundledAt": "2026-04-12T02:27:49.522Z",
+  "bundledFrom": "c191f35"
 }

package/bundled/dev-pipeline/reset-bug.sh

@@ -330,6 +330,8 @@ print('?')
     fi
 
     # -- Execute reset --
+    local _reset_tmpstderr _reset_stderr
+    _reset_tmpstderr=$(mktemp)
     if [[ "$DO_CLEAN" == true ]]; then
         log_info "Cleaning $CUR_BUG_ID (reset + delete artifacts)..."
         RESULT=$(python3 "$SCRIPTS_DIR/update-bug-status.py" \
@@ -337,14 +339,19 @@ print('?')
             --state-dir "$STATE_DIR" \
             --bug-id "$CUR_BUG_ID" \
             --project-root "$PROJECT_ROOT" \
-            --action clean 2>&1)
+            --action clean 2>"$_reset_tmpstderr")
     else
         log_info "Resetting $CUR_BUG_ID status..."
         RESULT=$(python3 "$SCRIPTS_DIR/update-bug-status.py" \
             --bug-list "$BUG_LIST" \
             --state-dir "$STATE_DIR" \
             --bug-id "$CUR_BUG_ID" \
-            --action reset 2>&1)
+            --action reset 2>"$_reset_tmpstderr")
+    fi
+    _reset_stderr=$(cat "$_reset_tmpstderr" 2>/dev/null || true)
+    rm -f "$_reset_tmpstderr"
+    if [[ -n "$_reset_stderr" ]]; then
+        log_warn "$_reset_stderr"
     fi
 
     # Check for errors

package/bundled/dev-pipeline/reset-feature.sh

@@ -340,6 +340,8 @@ print('?')
     fi
 
     # ── Execute reset ──
+    local _reset_tmpstderr _reset_stderr
+    _reset_tmpstderr=$(mktemp)
     if [[ "$DO_CLEAN" == true ]]; then
         log_info "Cleaning $CUR_FEATURE_ID (reset + delete artifacts)..."
         RESULT=$(python3 "$SCRIPTS_DIR/update-feature-status.py" \
@@ -348,14 +350,19 @@ print('?')
             --feature-id "$CUR_FEATURE_ID" \
             --feature-slug "$FEATURE_SLUG" \
             --project-root "$PROJECT_ROOT" \
-            --action clean 2>&1)
+            --action clean 2>"$_reset_tmpstderr")
     else
         log_info "Resetting $CUR_FEATURE_ID status..."
         RESULT=$(python3 "$SCRIPTS_DIR/update-feature-status.py" \
             --feature-list "$FEATURE_LIST" \
             --state-dir "$STATE_DIR" \
             --feature-id "$CUR_FEATURE_ID" \
-            --action reset 2>&1)
+            --action reset 2>"$_reset_tmpstderr")
+    fi
+    _reset_stderr=$(cat "$_reset_tmpstderr" 2>/dev/null || true)
+    rm -f "$_reset_tmpstderr"
+    if [[ -n "$_reset_stderr" ]]; then
+        log_warn "$_reset_stderr"
     fi
 
     # Check for errors

package/bundled/dev-pipeline/reset-refactor.sh

@@ -328,6 +328,8 @@ print('?')
     fi
 
     # -- Execute reset --
+    local _reset_tmpstderr _reset_stderr
+    _reset_tmpstderr=$(mktemp)
     if [[ "$DO_CLEAN" == true ]]; then
         log_info "Cleaning $CUR_REFACTOR_ID (reset + delete artifacts)..."
         RESULT=$(python3 "$SCRIPTS_DIR/update-refactor-status.py" \
@@ -335,14 +337,19 @@ print('?')
             --state-dir "$STATE_DIR" \
             --refactor-id "$CUR_REFACTOR_ID" \
             --project-root "$PROJECT_ROOT" \
-            --action clean 2>&1)
+            --action clean 2>"$_reset_tmpstderr")
     else
         log_info "Resetting $CUR_REFACTOR_ID status..."
         RESULT=$(python3 "$SCRIPTS_DIR/update-refactor-status.py" \
             --refactor-list "$REFACTOR_LIST" \
             --state-dir "$STATE_DIR" \
             --refactor-id "$CUR_REFACTOR_ID" \
-            --action reset 2>&1)
+            --action reset 2>"$_reset_tmpstderr")
+    fi
+    _reset_stderr=$(cat "$_reset_tmpstderr" 2>/dev/null || true)
+    rm -f "$_reset_tmpstderr"
+    if [[ -n "$_reset_stderr" ]]; then
+        log_warn "$_reset_stderr"
     fi
 
     # Check for errors

package/bundled/dev-pipeline/run-bugfix.sh

@@ -481,12 +481,38 @@ run_one() {
     # Initialize state if needed
     if [[ ! -f "$STATE_DIR/pipeline.json" ]]; then
         log_info "Initializing bugfix pipeline state..."
-        python3 "$SCRIPTS_DIR/init-bugfix-pipeline.py" \
+        local init_result init_stderr init_tmpstderr
+        init_tmpstderr=$(mktemp)
+        if ! init_result=$(python3 "$SCRIPTS_DIR/init-bugfix-pipeline.py" \
             --bug-list "$bug_list" \
-            --state-dir "$STATE_DIR" >/dev/null 2>&1 || {
-            log_error "Failed to initialize bugfix pipeline state"
+            --state-dir "$STATE_DIR" 2>"$init_tmpstderr"); then
+            init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+            rm -f "$init_tmpstderr"
+            if [[ -n "$init_stderr" ]]; then
+                log_warn "$init_stderr"
+            fi
+            log_error "Bugfix pipeline initialization failed (script error)"
             exit 1
-        }
+        fi
+        init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+        rm -f "$init_tmpstderr"
+
+        if [[ -n "$init_stderr" ]]; then
+            log_warn "$init_stderr"
+        fi
+
+        local init_valid
+        init_valid=$(echo "$init_result" | python3 -c "import sys,json; print(json.load(sys.stdin).get('valid', False))" 2>/dev/null || echo "False")
+
+        if [[ "$init_valid" != "True" ]]; then
+            log_error "Bugfix pipeline initialization failed:"
+            echo "$init_result"
+            exit 1
+        fi
+
+        local bugs_count
+        bugs_count=$(echo "$init_result" | python3 -c "import sys,json; print(json.load(sys.stdin).get('bugs_count', 0))" 2>/dev/null || echo "0")
+        log_success "Bugfix pipeline initialized with $bugs_count bugs"
 
         # Ensure state directory is gitignored
         local _gitignore_path
@@ -819,10 +845,25 @@ main() {
     # Initialize pipeline state if needed
     if [[ ! -f "$STATE_DIR/pipeline.json" ]]; then
         log_info "Initializing bugfix pipeline state..."
-        local init_result
-        init_result=$(python3 "$SCRIPTS_DIR/init-bugfix-pipeline.py" \
+        local init_result init_stderr init_tmpstderr
+        init_tmpstderr=$(mktemp)
+        if ! init_result=$(python3 "$SCRIPTS_DIR/init-bugfix-pipeline.py" \
             --bug-list "$bug_list" \
-            --state-dir "$STATE_DIR" 2>&1)
+            --state-dir "$STATE_DIR" 2>"$init_tmpstderr"); then
+            init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+            rm -f "$init_tmpstderr"
+            if [[ -n "$init_stderr" ]]; then
+                log_warn "$init_stderr"
+            fi
+            log_error "Bugfix pipeline initialization failed (script error)"
+            exit 1
+        fi
+        init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+        rm -f "$init_tmpstderr"
+
+        if [[ -n "$init_stderr" ]]; then
+            log_warn "$init_stderr"
+        fi
 
         local init_valid
         init_valid=$(echo "$init_result" | python3 -c "import sys,json; print(json.load(sys.stdin).get('valid', False))" 2>/dev/null || echo "False")

package/bundled/dev-pipeline/run-feature.sh

@@ -626,13 +626,26 @@ run_one() {
     # Initialize pipeline state if needed (same logic as run_all)
     if [[ ! -f "$STATE_DIR/pipeline.json" ]]; then
         log_info "Initializing pipeline state for single-feature run..."
-        local init_result
+        local init_result init_stderr init_tmpstderr
+        init_tmpstderr=$(mktemp)
         if ! init_result=$(python3 "$SCRIPTS_DIR/init-pipeline.py" \
             --feature-list "$feature_list" \
-            --state-dir "$STATE_DIR" 2>&1); then
+            --state-dir "$STATE_DIR" 2>"$init_tmpstderr"); then
+            init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+            rm -f "$init_tmpstderr"
+            if [[ -n "$init_stderr" ]]; then
+                log_warn "$init_stderr"
+            fi
             log_error "Pipeline initialization failed (script error)"
             exit 1
         fi
+        init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+        rm -f "$init_tmpstderr"
+
+        # Show any stderr warnings without corrupting JSON
+        if [[ -n "$init_stderr" ]]; then
+            log_warn "$init_stderr"
+        fi
 
         local init_valid
         init_valid=$(echo "$init_result" | python3 -c "import sys,json; print(json.load(sys.stdin).get('valid', False))" 2>/dev/null || echo "False")
@@ -1010,10 +1023,26 @@ main() {
     # Initialize pipeline state if needed
     if [[ ! -f "$STATE_DIR/pipeline.json" ]]; then
         log_info "Initializing pipeline state..."
-        local init_result
-        init_result=$(python3 "$SCRIPTS_DIR/init-pipeline.py" \
+        local init_result init_stderr init_tmpstderr
+        init_tmpstderr=$(mktemp)
+        if ! init_result=$(python3 "$SCRIPTS_DIR/init-pipeline.py" \
             --feature-list "$feature_list" \
-            --state-dir "$STATE_DIR" 2>&1)
+            --state-dir "$STATE_DIR" 2>"$init_tmpstderr"); then
+            init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+            rm -f "$init_tmpstderr"
+            if [[ -n "$init_stderr" ]]; then
+                log_warn "$init_stderr"
+            fi
+            log_error "Pipeline initialization failed (script error)"
+            exit 1
+        fi
+        init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+        rm -f "$init_tmpstderr"
+
+        # Show any stderr warnings (e.g. project root detection) without corrupting JSON
+        if [[ -n "$init_stderr" ]]; then
+            log_warn "$init_stderr"
+        fi
 
         local init_valid
         init_valid=$(echo "$init_result" | python3 -c "import sys,json; print(json.load(sys.stdin).get('valid', False))" 2>/dev/null || echo "False")

package/bundled/dev-pipeline/run-refactor.sh

@@ -508,12 +508,38 @@ run_one() {
     # Initialize state if needed
     if [[ ! -f "$STATE_DIR/pipeline.json" ]]; then
         log_info "Initializing refactor pipeline state..."
-        python3 "$SCRIPTS_DIR/init-refactor-pipeline.py" \
+        local init_result init_stderr init_tmpstderr
+        init_tmpstderr=$(mktemp)
+        if ! init_result=$(python3 "$SCRIPTS_DIR/init-refactor-pipeline.py" \
             --refactor-list "$refactor_list" \
-            --state-dir "$STATE_DIR" >/dev/null 2>&1 || {
-            log_error "Failed to initialize refactor pipeline state"
+            --state-dir "$STATE_DIR" 2>"$init_tmpstderr"); then
+            init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+            rm -f "$init_tmpstderr"
+            if [[ -n "$init_stderr" ]]; then
+                log_warn "$init_stderr"
+            fi
+            log_error "Refactor pipeline initialization failed (script error)"
             exit 1
-        }
+        fi
+        init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+        rm -f "$init_tmpstderr"
+
+        if [[ -n "$init_stderr" ]]; then
+            log_warn "$init_stderr"
+        fi
+
+        local init_valid
+        init_valid=$(echo "$init_result" | python3 -c "import sys,json; print(json.load(sys.stdin).get('valid', False))" 2>/dev/null || echo "False")
+
+        if [[ "$init_valid" != "True" ]]; then
+            log_error "Refactor pipeline initialization failed:"
+            echo "$init_result"
+            exit 1
+        fi
+
+        local refactors_count
+        refactors_count=$(echo "$init_result" | python3 -c "import sys,json; print(json.load(sys.stdin).get('refactors_count', 0))" 2>/dev/null || echo "0")
+        log_success "Refactor pipeline initialized with $refactors_count refactors"
 
         # Ensure state directory is gitignored
         local _gitignore_path
@@ -849,10 +875,25 @@ main() {
     # Initialize pipeline state if needed
     if [[ ! -f "$STATE_DIR/pipeline.json" ]]; then
         log_info "Initializing refactor pipeline state..."
-        local init_result
-        init_result=$(python3 "$SCRIPTS_DIR/init-refactor-pipeline.py" \
+        local init_result init_stderr init_tmpstderr
+        init_tmpstderr=$(mktemp)
+        if ! init_result=$(python3 "$SCRIPTS_DIR/init-refactor-pipeline.py" \
             --refactor-list "$refactor_list" \
-            --state-dir "$STATE_DIR" 2>&1)
+            --state-dir "$STATE_DIR" 2>"$init_tmpstderr"); then
+            init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+            rm -f "$init_tmpstderr"
+            if [[ -n "$init_stderr" ]]; then
+                log_warn "$init_stderr"
+            fi
+            log_error "Refactor pipeline initialization failed (script error)"
+            exit 1
+        fi
+        init_stderr=$(cat "$init_tmpstderr" 2>/dev/null || true)
+        rm -f "$init_tmpstderr"
+
+        if [[ -n "$init_stderr" ]]; then
+            log_warn "$init_stderr"
+        fi
 
         local init_valid
         init_valid=$(echo "$init_result" | python3 -c "import sys,json; print(json.load(sys.stdin).get('valid', False))" 2>/dev/null || echo "False")

package/bundled/dev-pipeline/scripts/init-pipeline.py

@@ -311,13 +311,27 @@ def main():
         print(json.dumps(output, indent=2, ensure_ascii=False))
         sys.exit(1)
 
-    # Warn if .prizmkit/plans/feature-list.json is not at project root
+    # Warn if feature-list.json is not under a recognizable project root.
+    # Walk up from the feature list directory to find a project root indicator.
     feature_list_dir = os.path.dirname(os.path.abspath(args.feature_list))
     indicators = ['.git', 'package.json', '.prizmkit']
-    is_at_root = any(os.path.exists(os.path.join(feature_list_dir, i)) for i in indicators)
-    if not is_at_root:
+
+    def _find_project_root(start_dir):
+        d = start_dir
+        while True:
+            if any(os.path.exists(os.path.join(d, ind)) for ind in indicators):
+                return d
+            parent = os.path.dirname(d)
+            if parent == d:
+                return None
+            d = parent
+
+    project_root = _find_project_root(feature_list_dir)
+    if project_root is None:
         sys.stderr.write(
-            "Warning: .prizmkit/plans/feature-list.json may not be at project root: {}\n".format(feature_list_dir)
+            "Warning: Could not find project root (no .git, package.json, or .prizmkit) above: {}\n".format(
+                feature_list_dir
+            )
         )
 
     # Validate schema

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.24",
+  "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.24",
+  "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": {