prizmkit 1.1.29 → 1.1.30

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.29",
-  "bundledAt": "2026-04-12T12:45:35.203Z",
-  "bundledFrom": "4dc0cee"
+  "frameworkVersion": "1.1.30",
+  "bundledAt": "2026-04-12T13:39:08.680Z",
+  "bundledFrom": "62d04b3"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.29",
+  "version": "1.1.30",
   "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/recovery-workflow/SKILL.md

@@ -22,27 +22,18 @@ User says:
 
 ## Pipeline Recovery (Recommended)
 
-For reliable recovery that completes ALL remaining phases autonomously, use the shell-driven pipeline:
+**IMPORTANT**: In Phase 1.3, you MUST present the user with a choice between pipeline recovery (`run-recovery.sh`) and interactive recovery. **NEVER skip this choice. NEVER decide for the user.** The pipeline approach is recommended because it generates a comprehensive bootstrap prompt that explicitly lists every remaining phase with full instructions, ensuring the AI completes the full workflow — not just the implementation part.
 
-```bash
-# Auto-detect and recover (with confirmation)
-./dev-pipeline/run-recovery.sh
-
-# Detection report only (no execution)
-./dev-pipeline/run-recovery.sh detect
-
-# Generate prompt without executing (inspect it)
-./dev-pipeline/run-recovery.sh run --dry-run
-
-# Skip confirmation (for scripted/daemon use)
-./dev-pipeline/run-recovery.sh run --yes
+Pipeline commands (for reference — Phase 1.3 will present these as a selectable option):
 
-# Override AI model
-./dev-pipeline/run-recovery.sh run --model claude-opus-4.6
+```bash
+./dev-pipeline/run-recovery.sh                    # Auto-detect and recover
+./dev-pipeline/run-recovery.sh detect              # Detection report only
+./dev-pipeline/run-recovery.sh run --dry-run       # Generate prompt, don't execute
+./dev-pipeline/run-recovery.sh run --yes           # Skip confirmation
+./dev-pipeline/run-recovery.sh run --model <model> # Override AI model
 ```
 
-The pipeline approach generates a comprehensive bootstrap prompt that explicitly lists every remaining phase with full instructions, ensuring the AI completes the full workflow — not just the implementation part.
-
 ### When to use pipeline vs interactive recovery
 
 | Scenario | Approach |
@@ -74,10 +65,10 @@ recovery-workflow
   │   ├── Based on artifact presence → infer current phase
   │   └── No match → reject and guide user
   │
-  ├── Phase 1: Report + user confirmation
+  ├── Phase 1: Report + user choice
   │   ├── Display detection results
   │   ├── If code changes exist → run test suite
-  │   └── User confirms "continue" → proceed
+  │   └── User chooses: run-recovery.sh (recommended) | interactive | start fresh
   │
   └── Phase 2: Execute remaining steps
       ├── Read target workflow's SKILL.md
@@ -169,18 +160,55 @@ Include test results in the report:
 - How many tests pass/fail
 - If failures exist — which tests and why
 
-### 1.3 Ask User to Confirm
+### 1.3 Ask User to Choose Recovery Approach
+
+**User choice required (mandatory)** — Use `AskUserQuestion` to present interactive selectable options. **NEVER skip this step. NEVER choose for the user.**
 
 ```
-Ready to resume from Phase 5 (Review). Continue?
+AskUserQuestion:
+  question: "Interrupted {workflow_type} detected at Phase {N} ({phase_name}). How would you like to recover?"
+  header: "Recovery"
+  options:
+    - label: "Run recovery script (Recommended)"
+      description: "Execute ./dev-pipeline/run-recovery.sh — autonomously completes ALL remaining phases (review, commit, merge, etc.) via a dedicated AI session with explicit phase instructions"
+    - label: "Copy command and run manually"
+      description: "I'll give you the exact shell command to paste into your terminal — you run it yourself outside this session"
+    - label: "Resume interactively in this session"
+      description: "Continue from Phase {N} within this conversation — more control, but may not complete all phases if session is interrupted again"
+    - label: "Start fresh"
+      description: "Discard interrupted work and restart the original workflow from scratch"
 ```
 
-If the user declines, suggest alternatives:
-- "Use `/bug-fix-workflow` to start fresh"
-- "Use `/feature-workflow` to start fresh"
-- "Use `/refactor-workflow` to start fresh"
+**If "Run recovery script"** → Execute the pipeline recovery:
+```bash
+./dev-pipeline/run-recovery.sh
+```
+The script handles everything: detection, confirmation, prompt generation, session spawn, and post-session validation. **End this skill after launching the script** — do not proceed to Phase 2.
+
+**If "Copy command and run manually"** → Output the command for the user to copy and run in their own terminal:
+```
+To recover, run this command in your project root:
+
+  ./dev-pipeline/run-recovery.sh
+
+Or with options:
+  ./dev-pipeline/run-recovery.sh run --dry-run    # Preview the recovery prompt first
+  ./dev-pipeline/run-recovery.sh run --yes         # Skip confirmation
+  ./dev-pipeline/run-recovery.sh run --model <model>  # Specify AI model
+```
+**End this skill** — do not proceed to Phase 2. The user will run the command themselves.
+
+**If "Resume interactively"** → Continue to Phase 2 below (execute remaining steps in this session).
+
+**If "Start fresh"** → Suggest the appropriate original workflow skill:
+- bug-fix-workflow → `/bug-fix-workflow`
+- feature-workflow → `/feature-workflow`
+- refactor-workflow → `/refactor-workflow`
+End this skill.
+
+**NEVER proceed to Phase 2 without explicit user selection via `AskUserQuestion`. Do NOT render options as plain text — the user must be able to click/select.**
 
-**CHECKPOINT CP-REC-1**: User confirmed recovery.
+**CHECKPOINT CP-REC-1**: User chose recovery approach.
 
 ---
 

package/package.json

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