rescue-planlisted
Install: claude install-skill vivekbhange-hub/legacy-rescue-skill
# rescue-plan
The other skills each answer one question. This one turns the answers into a plan a team can
run on Monday: what to do in the first 30, 60 and 90 days, in what order, how each phase is
known to be done, and what could go wrong. It invents nothing. Every item traces to a file in
`rescue/`, and anything the evidence does not cover is listed as a gap rather than guessed.
## Inputs
Read whichever exist; note which are missing:
| File | From | Used for |
|------|------|----------|
| `rescue/map.md` | rescue-map | system summary, commands, critical paths, unknowns |
| `rescue/hotspots.md` | rescue-hotspots | what to protect first, coupling, knowledge risk |
| `rescue/dead-code.md` | rescue-dead-code | deletion batches |
| `rescue/characterization.md` | rescue-characterize | which hotspots are pinned |
| `rescue/deps.md` | rescue-deps | upgrade steps and runtime deadlines |
| `rescue/strangler-*.md` | rescue-strangler | migration milestones and risks |
| `rescue/refactor-log.md` | rescue-refactor | progress so far |
Plus `$ARGUMENTS` and anything the user says about team size, deadlines, freeze periods and
business priorities.
## Output
- `rescue/PLAN.md`.
## Steps
1. **Check the evidence.** List which inputs exist. If `map.md` or `hotspots.md` is missing,
tell the user the plan will be thin and offer to run `rescue-map` / `rescue-hotspots` first.
Continue only if they agree to a partial plan; mark it "partial" in the title.
2. **Ask for the constraints