prizmkit 1.1.79 → 1.1.80

package/bundled/skills/prizmkit-plan/SKILL.md

@@ -86,89 +86,7 @@ A universal spec + plan generator. Takes a natural-language description of ANY d
 
 ## Examples
 
-### Example 1: New Feature
-
-**Input:** "I want users to upload avatars"
-
-**Phase 0 output:** `.prizmkit/specs/003-user-avatar/spec.md`
-```markdown
-# User Avatar Upload
-## Overview
-Allow registered users to upload and manage profile pictures.
-## Goals
-### G-1: Upload Avatar
-As a registered user, I want to upload a profile picture,
-so that other users can visually identify me.
-**Acceptance Criteria:**
-- Given I am on my profile page
-- When I select an image file and click upload
-- Then my avatar is updated and visible across the platform
-## Scope
-- **In scope:** Upload, display, remove avatar; image format validation
-- **Out of scope:** Image cropping/editing, avatar history
-```
-
-**Phase 1-2 output:** `plan.md` excerpt:
-```markdown
-## Tasks
-### Phase: Foundation (T-010~T-019)
-- [ ] [T-010] [G-1] Add avatar_url field to User model — file: src/models/user.ts
-- [ ] [T-011] [G-1] Create S3 upload utility — file: src/lib/s3.ts
-### Phase: Core [P] (T-100~T-109)
-- [ ] [T-100] [P] [G-1] POST /api/avatar upload endpoint — file: src/routes/avatar.ts
-```
-
-### Example 2: Refactoring
-
-**Input:** "Extract shared auth middleware from the API routes"
-
-**Phase 0 output:** `.prizmkit/specs/004-extract-auth-middleware/spec.md`
-```markdown
-# Extract Auth Middleware
-## Overview
-Consolidate duplicated authentication logic scattered across route files into a single shared middleware.
-## Goals
-### G-1: Extract Shared Authentication Logic
-Consolidate duplicated auth checks from 5 route files into a single middleware module.
-**Acceptance Criteria:**
-- All existing auth-related tests pass without modification
-- Auth logic exists in exactly one file (src/middleware/auth.ts)
-- No route file contains inline token verification
-## Scope
-- **In scope:** src/routes/users.ts, orders.ts, admin.ts, payments.ts, profile.ts
-- **Out of scope:** Authorization (role-based access), rate limiting
-## Behavior Preservation
-- All 23 existing API tests must pass unchanged
-- Response formats and HTTP status codes must not change
-- Error message strings must remain identical
-```
-
-### Example 3: Bug Fix
-
-**Input:** "Login page crashes when API returns 401"
-
-**Phase 0 output:** `.prizmkit/specs/005-login-401-crash/spec.md`
-```markdown
-# Fix: Login Crash on 401 Response
-## Overview
-Login page throws unhandled exception when auth API returns 401, causing a white screen.
-## Goals
-### G-1: Handle 401 Response Gracefully
-When the auth API returns 401, display an error message instead of crashing.
-**Acceptance Criteria:**
-- Given user submits invalid credentials, When API returns 401, Then error message "Invalid credentials" is displayed
-- Given user submits invalid credentials, When API returns 401, Then no unhandled exception is thrown
-## Root Cause
-- Error classification: Runtime
-- Root cause: `AuthService.handleLogin()` at src/services/auth.ts:42 does not handle null token
-- Affected files: src/services/auth.ts (L42), src/pages/login.tsx (L28)
-## Scope
-- **In scope:** Null handling in auth service, error display in login page
-- **Out of scope:** Other HTTP error codes (403, 500), auth flow redesign
-## Behavior Preservation
-- All existing login success tests must pass unchanged
-- Auth token flow for valid credentials must not change
-```
+Read `${SKILL_DIR}/references/examples.md` for worked examples of feature, refactoring, and bug fix planning.
 
 ## References
 

package/bundled/skills/prizmkit-plan/references/examples.md

@@ -0,0 +1,85 @@
+# Plan Examples
+
+## Example 1: New Feature
+
+**Input:** "I want users to upload avatars"
+
+**Phase 0 output:** `.prizmkit/specs/003-user-avatar/spec.md`
+```markdown
+# User Avatar Upload
+## Overview
+Allow registered users to upload and manage profile pictures.
+## Goals
+### G-1: Upload Avatar
+As a registered user, I want to upload a profile picture,
+so that other users can visually identify me.
+**Acceptance Criteria:**
+- Given I am on my profile page
+- When I select an image file and click upload
+- Then my avatar is updated and visible across the platform
+## Scope
+- **In scope:** Upload, display, remove avatar; image format validation
+- **Out of scope:** Image cropping/editing, avatar history
+```
+
+**Phase 1-2 output:** `plan.md` excerpt:
+```markdown
+## Tasks
+### Phase: Foundation (T-010~T-019)
+- [ ] [T-010] [G-1] Add avatar_url field to User model — file: src/models/user.ts
+- [ ] [T-011] [G-1] Create S3 upload utility — file: src/lib/s3.ts
+### Phase: Core [P] (T-100~T-109)
+- [ ] [T-100] [P] [G-1] POST /api/avatar upload endpoint — file: src/routes/avatar.ts
+```
+
+## Example 2: Refactoring
+
+**Input:** "Extract shared auth middleware from the API routes"
+
+**Phase 0 output:** `.prizmkit/specs/004-extract-auth-middleware/spec.md`
+```markdown
+# Extract Auth Middleware
+## Overview
+Consolidate duplicated authentication logic scattered across route files into a single shared middleware.
+## Goals
+### G-1: Extract Shared Authentication Logic
+Consolidate duplicated auth checks from 5 route files into a single middleware module.
+**Acceptance Criteria:**
+- All existing auth-related tests pass without modification
+- Auth logic exists in exactly one file (src/middleware/auth.ts)
+- No route file contains inline token verification
+## Scope
+- **In scope:** src/routes/users.ts, orders.ts, admin.ts, payments.ts, profile.ts
+- **Out of scope:** Authorization (role-based access), rate limiting
+## Behavior Preservation
+- All 23 existing API tests must pass unchanged
+- Response formats and HTTP status codes must not change
+- Error message strings must remain identical
+```
+
+## Example 3: Bug Fix
+
+**Input:** "Login page crashes when API returns 401"
+
+**Phase 0 output:** `.prizmkit/specs/005-login-401-crash/spec.md`
+```markdown
+# Fix: Login Crash on 401 Response
+## Overview
+Login page throws unhandled exception when auth API returns 401, causing a white screen.
+## Goals
+### G-1: Handle 401 Response Gracefully
+When the auth API returns 401, display an error message instead of crashing.
+**Acceptance Criteria:**
+- Given user submits invalid credentials, When API returns 401, Then error message "Invalid credentials" is displayed
+- Given user submits invalid credentials, When API returns 401, Then no unhandled exception is thrown
+## Root Cause
+- Error classification: Runtime
+- Root cause: `AuthService.handleLogin()` at src/services/auth.ts:42 does not handle null token
+- Affected files: src/services/auth.ts (L42), src/pages/login.tsx (L28)
+## Scope
+- **In scope:** Null handling in auth service, error display in login page
+- **Out of scope:** Other HTTP error codes (403, 500), auth flow redesign
+## Behavior Preservation
+- All existing login success tests must pass unchanged
+- Auth token flow for valid credentials must not change
+```

package/bundled/skills/prizmkit-prizm-docs/SKILL.md

@@ -36,6 +36,19 @@ This skill handles 6 operations. When invoked, determine the user's intent and e
 
 **Key principle**: `/prizmkit-prizm-docs` defines WHAT the docs should look like and bootstraps them. `/prizmkit-retrospective` is the SOLE WRITER that keeps docs in sync with code during ongoing development.
 
+### When to Use
+- First-time project documentation setup (init)
+- Checking if docs are up to date (status)
+- Rebuilding stale module docs after major changes (rebuild)
+- Validating doc format compliance (validate)
+- Migrating existing docs to Prizm format (migrate)
+- User says "initialize docs", "check doc status", "rebuild docs", "validate docs"
+
+### When NOT to Use
+- Incremental doc updates after code changes → use /prizmkit-retrospective (the sole writer during development)
+- Project has no .prizmkit/prizm-docs/ and user doesn't want to initialize
+- User wants to edit code → use /prizmkit-plan and /prizmkit-implement
+
 ## Operation: Init
 
 Bootstrap .prizmkit/prizm-docs/ for the current project.

package/bundled/skills/prizmkit-test/SKILL.md

@@ -108,94 +108,11 @@ Compare what exists against what should exist, across three levels:
 
 ### Phase 4: Generate Missing Tests
 
-Generate tests in priority order: unit → integration → E2E. After each batch, run immediately.
-
-When generated tests fail, distinguish two cases:
-- **Test bug** (syntax error, wrong import, wrong mock, wrong framework API usage) → fix the test and re-run
-- **Assertion failure** (test is valid but code returns unexpected result) → mark as "needs review" in report; do NOT modify production code. This is a potential bug discovered by the generated test.
-
-If a test fails repeatedly after 2 fix attempts, skip it and mark as "unresolved" in the report.
-
-**4a. Unit Tests (always applicable)**
-
-For each uncovered interface:
-- Read the source file to understand function signature and logic
-- Generate test file matching project conventions (framework, naming, directory, import style, mock/fixture patterns)
-- Common naming patterns to match:
-  - `src/foo.ts` → `src/__tests__/foo.test.ts` or `src/foo.spec.ts` or `tests/foo_test.py`
-  - Mirror the existing pattern; if no tests exist, use the framework's default convention
-- Cover: happy path, edge cases (null/undefined/empty), error conditions, boundary values
-- Do NOT test framework internals or third-party library behavior
-- Run tests immediately after generating
-
-**4b. Integration Tests**
-
-For each module with dependencies:
-- Generate tests for the module's primary interface exercising its real dependencies
-- If API endpoints exist: request/response tests (valid input, invalid input, missing params, auth)
-- If database operations exist: CRUD tests using the project's existing test database config
-- Run tests immediately after generating
-
-**4c. E2E Tests (conditional)**
-
-Preconditions (ALL must be met):
-- Playwright is available (`@playwright/test` or `playwright` in package.json dependencies, or `npx playwright --version` succeeds as fallback)
-- Playwright browsers are installed (check `npx playwright install --dry-run 2>/dev/null` exits cleanly, or `node_modules/.cache/ms-playwright/` directory exists; if missing, warn in report and skip E2E)
-- Project has a UI layer
-- Project can be started (start/dev script in package.json)
-- Acceptance criteria exist in spec.md files
-
-If ALL met:
-- **Before starting dev server**: detect whether it's already running: (1) check `package.json` scripts for port flags (`--port`, `-p`, `PORT=`), (2) fall back to framework defaults (3000 for React/Next/Express, 5173 for Vite, 8000 for Django, 5000 for Flask), (3) if still unknown, ask the user. Use the detected port in `lsof -i :<port>` to check. If running, tell user: "Dev server appears to be already running on port {N}. Use this running instance for E2E tests?" If user confirms, use existing instance. If user declines, skip E2E.
-- Start the project dev server (only if not already running). Wait for it to be ready.
-- For each uncovered acceptance criterion, generate a Playwright test script
-- Run generated E2E tests, capture screenshots of failures
-- **Only stop dev server if you started it.** Never stop a server that was already running.
-
-If NOT met:
-- Note what was skipped and why in the report
-- If only the server wasn't startable: still generate E2E script files but mark as "not run — manual execution needed"
+Read `${SKILL_DIR}/references/test-generation-steps.md` for the detailed generation procedure — priority order (unit → integration → E2E), failure handling rules, and generation patterns for each test level.
 
 ### Phase 5: Unified Report
 
-Create `.prizmkit/test/{YYYY_MM_DD_HH_MM_SS}_testresult/` directory.
-
-**test-report.md** format:
-
-```markdown
-# Test Report — {timestamp}
-
-## Summary
-- Scope: {full / module: name / feature: ###-name}
-- Architecture: {frontend / backend / fullstack}
-- Test framework: {name}
-- Mode: {interactive / headless}
-
-## Existing Tests
-- Total: {N} | Passed: {N} | Failed: {N}
-{failed test details or "All passing"}
-{or "No existing tests found — generated first batch"}
-
-## Coverage Gaps Found
-| Module | Interface | Type | Status |
-|--------|-----------|------|--------|
-| ... | ... | unit/integration/e2e | covered / generated / needs-review / unresolved / skipped |
-
-## Generated Tests
-- Unit: {N} generated, {N} needs-review, {N} unresolved
-- Integration: {N} generated, {N} needs-review, {N} unresolved
-- E2E: {N} generated, {N} skipped ({reason})
-
-## Final Status
-- All tests passing: {yes / no}
-- Needs human review: {list of tests marked needs-review}
-{remaining failures if any}
-```
-
-Also save:
-- `existing-test-output.txt` — raw output from Phase 2
-- `generated-tests/` — copies of all generated test files
-- `e2e-output/` — E2E logs and failure screenshots (if applicable)
+Create `.prizmkit/test/{YYYY_MM_DD_HH_MM_SS}_testresult/` directory. Read `${SKILL_DIR}/references/test-report-template.md` for the full report format and artifact list.
 
 ## Output
 
@@ -211,71 +128,6 @@ If the session is interrupted:
 
 ## Examples
 
-### Example 1: Full-Project Quality Check with Test Generation
-
-**User**: `/prizmkit-test`
-
-**Phase 0 — Architecture Detection**:
-```
-Detected: Fullstack (React + Express)
-Test framework: Vitest (7 existing test files)
-```
-
-**Phase 1 — Scope Selection** (user selects option 1):
-```
-Scope: Full project (all modules, all specs)
-```
-
-**Phase 2 — Existing Tests**: 7 test files found, 20 tests run, 18 passed, 2 pre-existing failures (recorded, not fixed).
-
-**Phase 3 — Gap Analysis** (excerpt):
-| Module | Interface | Type | Status |
-|--------|-----------|------|--------|
-| auth | login() | unit | missing |
-| auth | register() | unit | missing |
-| payment | processPayment() | unit | missing |
-| payment | api/checkout | integration | missing |
-| — | Checkout flow | e2e | missing |
-
-**Phase 4**: Generated 5 unit tests (3 passing, 2 assertion failures marked "needs-review"), 1 integration test (passing), 1 E2E test (passing).
-
-**Phase 5 — Report Summary**:
-```
-Generated: 5 unit (2 needs-review), 1 integration, 1 E2E
-Report: .prizmkit/test/2026_05_23_14_30_00_testresult/test-report.md
-Needs human review: processPayment (returns 400 for negative amounts, expected 422), refund (missing authorization header causes 500 instead of 401)
-```
-
-### Example 2: Single-Feature Targeted Test
-
-**User**: `/prizmkit-test`
-
-**Phase 0 — Architecture Detection**:
-```
-Detected: Backend (Express)
-Test framework: Vitest
-```
-
-**Phase 1 — Scope Selection** (user selects option 3, then picks "042-payment-gateway"):
-```
-Scope: Single feature — 042-payment-gateway
-Test files in scope: 2
-
-**Phase 2 — Existing Tests**: 2 test files, 8 tests, all passing.
-
-**Phase 3 — Gap Analysis** (excerpt):
-| Module | Interface | Type | Status |
-|--------|-----------|------|--------|
-| payment | processPayment() | unit | missing |
-| payment | refund() | unit | missing |
-
-**Phase 4**: Generated 2 unit tests (both passing). No integration/E2E applicable for this scope.
-
-**Phase 5 — Report Summary**:
-```
-Generated: 2 unit tests (all passing)
-Report: .prizmkit/test/2026_05_23_15_00_00_testresult/test-report.md
-All tests passing. Ready for commit.
-```
+Read `${SKILL_DIR}/references/examples.md` for worked examples of full-project and single-feature test runs.
 
 **HANDOFF:** Independent skill — no handoff. User may proceed to `/prizmkit-committer` if all tests pass, or fix issues manually if tests are marked "needs-review".

package/bundled/skills/prizmkit-test/references/examples.md

@@ -0,0 +1,70 @@
+# Test Examples
+
+## Example 1: Full-Project Quality Check with Test Generation
+
+**User**: `/prizmkit-test`
+
+**Phase 0 — Architecture Detection**:
+```
+Detected: Fullstack (React + Express)
+Test framework: Vitest (7 existing test files)
+```
+
+**Phase 1 — Scope Selection** (user selects option 1):
+```
+Scope: Full project (all modules, all specs)
+```
+
+**Phase 2 — Existing Tests**: 7 test files found, 20 tests run, 18 passed, 2 pre-existing failures (recorded, not fixed).
+
+**Phase 3 — Gap Analysis** (excerpt):
+| Module | Interface | Type | Status |
+|--------|-----------|------|--------|
+| auth | login() | unit | missing |
+| auth | register() | unit | missing |
+| payment | processPayment() | unit | missing |
+| payment | api/checkout | integration | missing |
+| — | Checkout flow | e2e | missing |
+
+**Phase 4**: Generated 5 unit tests (3 passing, 2 assertion failures marked "needs-review"), 1 integration test (passing), 1 E2E test (passing).
+
+**Phase 5 — Report Summary**:
+```
+Generated: 5 unit (2 needs-review), 1 integration, 1 E2E
+Report: .prizmkit/test/2026_05_23_14_30_00_testresult/test-report.md
+Needs human review: processPayment (returns 400 for negative amounts, expected 422), refund (missing authorization header causes 500 instead of 401)
+```
+
+## Example 2: Single-Feature Targeted Test
+
+**User**: `/prizmkit-test`
+
+**Phase 0 — Architecture Detection**:
+```
+Detected: Backend (Express)
+Test framework: Vitest
+```
+
+**Phase 1 — Scope Selection** (user selects option 3, then picks "042-payment-gateway"):
+```
+Scope: Single feature — 042-payment-gateway
+Test files in scope: 2
+
+**Phase 2 — Existing Tests**: 2 test files, 8 tests, all passing.
+
+**Phase 3 — Gap Analysis** (excerpt):
+| Module | Interface | Type | Status |
+|--------|-----------|------|--------|
+| payment | processPayment() | unit | missing |
+| payment | refund() | unit | missing |
+
+**Phase 4**: Generated 2 unit tests (both passing). No integration/E2E applicable for this scope.
+
+**Phase 5 — Report Summary**:
+```
+Generated: 2 unit tests (all passing)
+Report: .prizmkit/test/2026_05_23_15_00_00_testresult/test-report.md
+All tests passing. Ready for commit.
+```
+
+**HANDOFF**: Independent skill — no handoff. User may proceed to `/prizmkit-committer` if all tests pass, or fix issues manually if tests are marked "needs-review".

package/bundled/skills/prizmkit-test/references/test-generation-steps.md

@@ -0,0 +1,49 @@
+# Test Generation Steps (Phase 4)
+
+Generate tests in priority order: unit → integration → E2E. After each batch, run immediately.
+
+When generated tests fail, distinguish two cases:
+- **Test bug** (syntax error, wrong import, wrong mock, wrong framework API usage) → fix the test and re-run
+- **Assertion failure** (test is valid but code returns unexpected result) → mark as "needs review" in report; do NOT modify production code. This is a potential bug discovered by the generated test.
+
+If a test fails repeatedly after 2 fix attempts, skip it and mark as "unresolved" in the report.
+
+## 4a. Unit Tests (always applicable)
+
+For each uncovered interface:
+- Read the source file to understand function signature and logic
+- Generate test file matching project conventions (framework, naming, directory, import style, mock/fixture patterns)
+- Common naming patterns to match:
+  - `src/foo.ts` → `src/__tests__/foo.test.ts` or `src/foo.spec.ts` or `tests/foo_test.py`
+  - Mirror the existing pattern; if no tests exist, use the framework's default convention
+- Cover: happy path, edge cases (null/undefined/empty), error conditions, boundary values
+- Do NOT test framework internals or third-party library behavior
+- Run tests immediately after generating
+
+## 4b. Integration Tests
+
+For each module with dependencies:
+- Generate tests for the module's primary interface exercising its real dependencies
+- If API endpoints exist: request/response tests (valid input, invalid input, missing params, auth)
+- If database operations exist: CRUD tests using the project's existing test database config
+- Run tests immediately after generating
+
+## 4c. E2E Tests (conditional)
+
+Preconditions (ALL must be met):
+- Playwright is available (`@playwright/test` or `playwright` in package.json dependencies, or `npx playwright --version` succeeds as fallback)
+- Playwright browsers are installed (check `npx playwright install --dry-run 2>/dev/null` exits cleanly, or `node_modules/.cache/ms-playwright/` directory exists; if missing, warn in report and skip E2E)
+- Project has a UI layer
+- Project can be started (start/dev script in package.json)
+- Acceptance criteria exist in spec.md files
+
+If ALL met:
+- **Before starting dev server**: detect whether it's already running: (1) check `package.json` scripts for port flags (`--port`, `-p`, `PORT=`), (2) fall back to framework defaults (3000 for React/Next/Express, 5173 for Vite, 8000 for Django, 5000 for Flask), (3) if still unknown, ask the user. Use the detected port in `lsof -i :<port>` to check. If running, tell user: "Dev server appears to be already running on port {N}. Use this running instance for E2E tests?" If user confirms, use existing instance. If user declines, skip E2E.
+- Start the project dev server (only if not already running). Wait for it to be ready.
+- For each uncovered acceptance criterion, generate a Playwright test script
+- Run generated E2E tests, capture screenshots of failure.
+- **Only stop dev server if you started it.** Never stop a server that was already running.
+
+If NOT met:
+- Note what was skipped and why in the report
+- If only the server wasn't startable: still generate E2E script files but mark as "not run — manual execution needed"

package/bundled/skills/prizmkit-test/references/test-report-template.md

@@ -0,0 +1,42 @@
+# Test Report Output Template
+
+Used in Phase 5 of `/prizmkit-test`. Create `.prizmkit/test/{YYYY_MM_DD_HH_MM_SS}_testresult/` directory and write `test-report.md`.
+
+## test-report.md Format
+
+```markdown
+# Test Report — {timestamp}
+
+## Summary
+- Scope: {full / module: name / feature: ###-name}
+- Architecture: {frontend / backend / fullstack}
+- Test framework: {name}
+- Mode: {interactive / headless}
+
+## Existing Tests
+- Total: {N} | Passed: {N} | Failed: {N}
+{failed test details or "All passing"}
+{or "No existing tests found — generated first batch"}
+
+## Coverage Gaps Found
+| Module | Interface | Type | Status |
+|--------|-----------|------|--------|
+| ... | ... | unit/integration/e2e | covered / generated / needs-review / unresolved / skipped |
+
+## Generated Tests
+- Unit: {N} generated, {N} needs-review, {N} unresolved
+- Integration: {N} generated, {N} needs-review, {N} unresolved
+- E2E: {N} generated, {N} skipped ({reason})
+
+## Final Status
+- All tests passing: {yes / no}
+- Needs human review: {list of tests marked needs-review}
+{remaining failures if any}
+```
+
+## Artifacts
+
+Also save alongside `test-report.md`:
+- `existing-test-output.txt` — raw output from Phase 2
+- `generated-tests/` — copies of all generated test files
+- `e2e-output/` — E2E logs and failure screenshots (if applicable)

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

@@ -88,36 +88,7 @@ recovery-workflow
 
 Run the detection script:
 
-```bash
-python3 ${SKILL_DIR}/scripts/detect-recovery-state.py
-```
-
-The script uses **priority-ordered signature matching**:
-
-```
-1. Current branch matches fix/*           → bug-fix-workflow
-2. .prizmkit/bugfix/ directory has content → bug-fix-workflow
-3. Current branch matches refactor/*       → refactor-workflow
-4. .prizmkit/plans/refactor-list.json exists               → refactor-workflow
-5. Current branch matches feat/*           → feature-workflow
-6. .prizmkit/plans/feature-list.json exists                → feature-workflow
-7. None of the above                       → no workflow detected
-```
-
-Bug-fix-workflow has highest priority because it is purely interactive and benefits most from recovery (no pipeline retry fallback).
-
-### If no workflow detected
-
-Show guidance and exit:
-
-```
-No interrupted workflow detected in this workspace.
-
-To start a new workflow:
-  • /feature-workflow   — build features from idea to code
-  • /bug-fix-workflow   — fix a specific bug interactively
-  • /refactor-workflow  — behavior-preserving code restructuring
-```
+Run the detection script (`python3 ${SKILL_DIR}/scripts/detect-recovery-state.py`). For the full signature matching table, phase inference tables (bug-fix/feature/refactor), and no-workflow-detected guidance, read `${SKILL_DIR}/references/detection.md`.
 
 **CHECKPOINT CP-REC-0**: Workflow type and phase identified.
 

package/bundled/skills/recovery-workflow/references/detection.md

@@ -0,0 +1,58 @@
+# Recovery Phase Detection
+
+The script uses **priority-ordered signature matching**:
+
+```
+1. Current branch matches fix/*           → bug-fix-workflow
+2. .prizmkit/bugfix/ directory has content → bug-fix-workflow
+3. Current branch matches refactor/*       → refactor-workflow
+4. .prizmkit/plans/refactor-list.json exists               → refactor-workflow
+5. Current branch matches feat/*           → feature-workflow
+6. .prizmkit/plans/feature-list.json exists                → feature-workflow
+7. None of the above                       → no workflow detected
+```
+
+Bug-fix-workflow has highest priority because it is purely interactive and benefits most from recovery (no pipeline retry fallback).
+
+## If No Workflow Detected
+
+Show guidance and exit:
+
+```
+No interrupted workflow detected in this workspace.
+
+To start a new workflow:
+  • /feature-workflow   — build features from idea to code
+  • /bug-fix-workflow   — fix a specific bug interactively
+  • /refactor-workflow  — behavior-preserving code restructuring
+```
+
+## Phase Inference Tables
+
+### Bug-Fix-Workflow Recovery
+
+| Detected State | Resume From | Actions |
+|---------------|------------|---------|
+| On `fix/<BUG_ID>-*` branch, no artifacts | Phase 1: Deep Bug Diagnosis | Read bug description from `.prizmkit/plans/bug-fix-list.json`. Start interactive diagnosis Q&A |
+| `fix-plan.md` exists, no code changes | Phase 4: Fix | Read fix-plan.md. Implement the fix following the plan |
+| `fix-plan.md` + code changes exist | Phase 5: Review | Invoke `/prizmkit-code-review` on all changes |
+| All docs + review passed | Phase 6: User Verification | Ask user to verify the fix works |
+| All docs + committed | Phase 7: Merge Decision | Ask merge vs keep branch |
+
+Note: Bug-fix Phases 1-3 (Diagnosis, Triage, Reproduce) collapse to Phase 1 because they don't produce persistent artifacts. If interrupted during these phases, recovery restarts from Phase 1.
+
+### Feature-Workflow Recovery
+
+| Detected State | Resume From | Actions |
+|---------------|------------|---------|
+| No `.prizmkit/plans/feature-list.json` | Phase 1: Brainstorm | Cannot recover conversation context. Start requirement clarification, leverage workspace content |
+| `.prizmkit/plans/feature-list.json` exists, no pipeline state | Phase 3: Launch | Invoke `feature-pipeline-launcher` |
+| `.prizmkit/plans/feature-list.json` + pipeline state exists | Phase 4: Monitor | Check pipeline status via `feature-pipeline-launcher` (Intent B) |
+
+### Refactor-Workflow Recovery
+
+| Detected State | Resume From | Actions |
+|---------------|------------|---------|
+| No `.prizmkit/plans/refactor-list.json` | Phase 1: Brainstorm | Start refactoring goal clarification |
+| `.prizmkit/plans/refactor-list.json` exists, no pipeline state | Phase 3: Launch | Invoke `refactor-pipeline-launcher` |
+| `.prizmkit/plans/refactor-list.json` + pipeline state exists | Phase 4: Monitor | Check pipeline status |