prizmkit 1.1.111 → 1.1.112

package/bundled/skills/recovery-workflow/evals/evals.json

@@ -1,45 +1,53 @@
 {
   "skill_name": "recovery-workflow",
-  "notes": "These test cases require workspace state setup. Each has a setup_description that creates the necessary mock state before the skill is invoked. Due to the interactive nature and state-dependency of this skill, automated evaluation is limited — qualitative review is primary.",
+  "notes": "These test cases require workspace state setup. Recovery now treats fix-plan.md and fix-report.md as optional signals; branch, diff, spec.md, plan.md, review artifacts, and pipeline state are also valid recovery signals.",
   "evals": [
     {
       "id": 1,
-      "name": "bugfix-mid-fix",
+      "name": "bugfix-mid-fix-with-plan",
       "prompt": "My session broke, help me recover",
-      "expected_output": "Should auto-detect bug-fix-workflow from fix/B-001-* branch. Should detect fix-plan.md + code changes → infer Phase 5 (Review). Should display recovery report with workflow type, phase, artifacts, code stats. After user confirms, should invoke /prizmkit-code-review on existing changes.",
-      "setup_description": "Create fix/B-001-login-crash branch, .prizmkit/bugfix/B-001/fix-plan.md, modify 3 source files + 1 test file. No fix-report.md, no commits ahead of main.",
+      "expected_output": "Should auto-detect bug-fix-workflow from fix/B-001-* branch. Should detect fix-plan.md + code changes as optional plan signal plus implementation diff -> infer Review. Should display recovery report with workflow type, phase, artifacts, and code stats. Should ask recovery approach before invoking /prizmkit-code-review or recovery script.",
+      "setup_description": "Create fix/B-001-login-crash branch, optional .prizmkit/bugfix/B-001/fix-plan.md, modify 3 source files + 1 test file. No fix-report.md, no commits ahead of main.",
       "files": []
     },
     {
       "id": 2,
+      "name": "bugfix-diff-no-fix-plan",
+      "prompt": "Continue the previous bug fix",
+      "expected_output": "Should auto-detect bug-fix-workflow from fix/B-002-* branch even without fix-plan.md. Code/test changes should infer Review. Should not require .prizmkit/bugfix/B-002/fix-plan.md to exist.",
+      "setup_description": "Create fix/B-002-null-pointer branch and modify 2 source files + 1 test file. No .prizmkit/bugfix/B-002 directory, no fix-plan.md, no fix-report.md.",
+      "files": []
+    },
+    {
+      "id": 3,
       "name": "bugfix-plan-only",
       "prompt": "Continue the previous work",
-      "expected_output": "Should auto-detect bug-fix-workflow from fix/B-002-* branch. Should detect fix-plan.md but no code changes → infer Phase 4 (Fix). Should read fix-plan.md and start implementing the fix.",
-      "setup_description": "Create fix/B-002-null-pointer branch, .prizmkit/bugfix/B-002/fix-plan.md with diagnosis and fix approach. No code changes.",
+      "expected_output": "Should auto-detect bug-fix-workflow from fix/B-003-* branch. Should detect spec.md or plan.md but no code changes -> infer Fix. Should read the plan artifact and resume implementation only after user chooses interactive recovery.",
+      "setup_description": "Create fix/B-003-null-pointer branch with spec.md and plan.md. No code changes.",
       "files": []
     },
     {
-      "id": 3,
+      "id": 4,
       "name": "feature-list-exists",
       "prompt": "resume",
-      "expected_output": "Should auto-detect feature-workflow from .prizmkit/plans/feature-list.json. Should detect .prizmkit/plans/feature-list.json exists but no pipeline state → infer Phase 3 (Launch). Should invoke feature-pipeline-launcher to start the pipeline.",
+      "expected_output": "Should auto-detect feature-workflow from .prizmkit/plans/feature-list.json. Should detect list exists but no pipeline state -> infer Launch. Should ask recovery approach; launcher handoff is valid after user selection.",
       "setup_description": "On main branch, create .prizmkit/plans/feature-list.json with 3 features. No .prizmkit/state/features/ directory.",
       "files": []
     },
     {
-      "id": 4,
+      "id": 5,
       "name": "refactor-monitoring",
       "prompt": "pick up where it left off",
-      "expected_output": "Should auto-detect refactor-workflow from .prizmkit/plans/refactor-list.json + pipeline state. Should infer Phase 4 (Monitor). Should check pipeline status and report results.",
+      "expected_output": "Should auto-detect refactor-workflow from .prizmkit/plans/refactor-list.json + pipeline state. Should infer Monitor / Recover Pipeline. Should ask whether to run recovery script, resume interactively, clean retry, or start fresh.",
       "setup_description": "On main branch, create .prizmkit/plans/refactor-list.json with 2 items. Create .prizmkit/state/refactor/ with status files showing 1 completed, 1 in-progress.",
       "files": []
     },
     {
-      "id": 5,
+      "id": 6,
       "name": "no-workflow-detected",
       "prompt": "recover",
-      "expected_output": "Should detect no workflow signatures in workspace. Should display guidance message suggesting /feature-workflow, /bug-fix-workflow, or /refactor-workflow. Should NOT attempt any recovery actions.",
-      "setup_description": "Clean workspace on main branch. No .prizmkit/plans/feature-list.json, no bug-fix artifacts, no .prizmkit/plans/refactor-list.json, no fix/* or feat/* or refactor/* branches.",
+      "expected_output": "Should detect no workflow signatures in workspace. Should display guidance suggesting /feature-workflow, /bug-fix-workflow, or /refactor-workflow. Should NOT attempt recovery actions.",
+      "setup_description": "Clean workspace on main branch. No .prizmkit/plans/*.json files, no pipeline state, no fix/* or feat/* or refactor/* branch, no spec.md or plan.md.",
       "files": []
     }
   ]

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

@@ -1,58 +1,67 @@
 # Recovery Phase Detection
 
-The script uses **priority-ordered signature matching**:
+Detection uses priority-ordered signals, but no single signal is authoritative. Prefer a conservative recovery phase when signals disagree.
 
-```
-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
-```
+## Signature Priority
+
+1. Current branch starts with `fix/` -> likely `bug-fix-workflow`.
+2. `.prizmkit/state/bugfix/` or `.prizmkit/plans/bug-fix-list.json` has relevant failed/in-progress state -> likely bugfix pipeline.
+3. `.prizmkit/bugfix/` has optional bugfix artifacts -> possible `bug-fix-workflow`.
+4. Current branch starts with `refactor/` -> likely `refactor-workflow`.
+5. `.prizmkit/plans/refactor-list.json` or `.prizmkit/state/refactor/` exists -> likely refactor pipeline.
+6. Current branch starts with `feat/` -> likely `feature-workflow`.
+7. `.prizmkit/plans/feature-list.json` or `.prizmkit/state/features/` exists -> likely feature pipeline.
+8. `spec.md` or `plan.md` exists without family-specific signals -> current-workspace Fast Path; ask which workflow it belongs to.
+9. 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).
+Bug-fix signals are prioritized because interactive bug recovery benefits most from preserving local diagnosis and fix work.
 
-## If No Workflow Detected
+## Optional vs Required Artifacts
+
+`fix-plan.md` and `fix-report.md` are optional bug recovery signals. They are useful when present, but bug-fix recovery must also infer from branch, diff, `spec.md`, `plan.md`, review artifacts, commits, and bug-list entries.
+
+## If No Workflow Is Detected
 
 Show guidance and exit:
 
-```
-No interrupted workflow detected in this workspace.
+```markdown
+No interrupted workflow was 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
+Start a new workflow:
+- /feature-workflow — build features from idea to code
+- /bug-fix-workflow — fix a specific bug interactively
+- /refactor-workflow — restructure code while preserving behavior
 ```
 
 ## Phase Inference Tables
 
-### Bug-Fix-Workflow Recovery
+### Bug-Fix 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 |
+| Detected state | Resume from | Actions |
+|---|---|---|
+| `fix/*` branch, no implementation artifacts | Diagnosis / triage | Restore bug context, confirm understanding, choose next action |
+| `spec.md` or `plan.md`, no code changes | Fix | Read plan and implement the root-cause fix |
+| Optional `fix-plan.md`, no code changes | Fix | Read fix plan and implement the fix |
+| Code/test changes, no review artifact | Review | Run tests if safe, then invoke `/prizmkit-code-review` |
+| Review artifact or optional `fix-report.md` | User verification | Ask user whether to verify manually before commit |
+| Commit ahead on fix branch | Merge decision | Ask merge / keep branch / decide later |
 
-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.
+Bug-fix diagnosis, triage, and reproduction do not always create durable artifacts. If interrupted before code changes or a plan artifact, restart from diagnosis rather than guessing.
 
-### Feature-Workflow Recovery
+### Feature 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) |
+| Detected state | Resume from | Actions |
+|---|---|---|
+| No feature list and no Fast Path artifacts | Route selection | Clarify whether to plan, implement Fast Path, or start app planning |
+| `spec.md` or `plan.md` with feature context | Fast Path continuation | Continue implementation, review, retrospective, or commit based on diff |
+| `.prizmkit/plans/feature-list.json`, no pipeline state | Launch | Invoke `feature-pipeline-launcher` |
+| Feature list plus `.prizmkit/state/features/` | Monitor/recover | Check launcher status or run recovery script |
 
-### Refactor-Workflow Recovery
+### Refactor 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 |
+| Detected state | Resume from | Actions |
+|---|---|---|
+| No refactor list and no Fast Path artifacts | Route selection | Clarify behavior-preserving refactor goal |
+| `spec.md` or `plan.md` with refactor context | Fast Path continuation | Continue implementation, behavior checks, review, retrospective, or commit |
+| `.prizmkit/plans/refactor-list.json`, no pipeline state | Launch | Invoke `refactor-pipeline-launcher` |
+| Refactor list plus `.prizmkit/state/refactor/` | Monitor/recover | Check launcher status or run recovery script |