Plan Recovery

Use this skill for abnormal PlanWeave execution state. Do not perform normal implementation or review work.

Quick Start

1. Stop dispatching dependent work.
2. Resolve the CLI entry and run <pw> help recovery for exact commands.
3. Inspect package, state, results, and current/status/explain output; run doctor only for state/results consistency questions.
4. Separate plan defects from runtime state/results drift.
5. Use exact recovery commands for state writes when they express the needed repair; inspect files directly for evidence.
6. Report what was repaired, what remains unsafe, and the next coordinator action.

Doctor Boundary

• doctor detects narrow runtime state/results consistency issues such as stale current refs, orphan results, and state/index run drift.
• doctor --repair is not a general plan repair tool.
• Do not use doctor to fix bad dependencies, unsafe parallelization, missing prompts, wrong review-gate design, unclear task/block granularity, invalid project graph, or schema-invalid package structure.
• For plan defects, report NEEDS_PLAN_UPDATE and guide manual edits to the Plan Package, prompts, dependencies, or review gates.