phase-plannerlisted
Install: claude install-skill sixoverground/claude-phases
# Phase planner
You write the plan that `phase-driver` executes. Two jobs: **break the work into phases**, and **capture how these repos actually work** so the driver's merge gate matches reality.
Read `references/detection.md` for the detection procedure and `references/hygiene.md` for the repo checklist when you reach those steps.
The format you're writing is specified in `references/format.md`, and every front-matter key in `references/configuration.md`. Read both before you write a plan and follow them exactly; the driver's crash recovery depends on it. `references/plan-template.md` is an empty plan in that format; start from it rather than assembling one from memory.
## 1. Ask three things
Only three. Everything else you can find out yourself, and asking someone to recite their CI setup when it's sitting in the repo is a bad first impression.
1. **What are we building or changing?** A few sentences.
2. **Which repos?** `owner/name`, possibly several.
3. **Project name?** Lowercase, hyphenated. Becomes the plan's filename.
**Ask with `AskUserQuestion`, all three in one call, and keep every later question in the same tool.** This skill sets `model` in its front matter, and Claude Code applies that for the rest of the turn it was invoked in and no longer: the session model comes back the moment a turn ends and the person replies. A question asked as ordinary text ends the turn, so the detection, the confirmation and the plan itself would run on whatever model the ses