phase-decomposelisted

Use to turn a large goal into a well-chunked umbrella roadmap before any phase work starts. Trigger when the user hands over a big feature or project and says "break this down", "decompose this", "chunk this into phases", "plan out this whole thing", "make a roadmap", or when phase-loop needs an umbrella to drive. Produces the MAJOR.0.0 umbrella plan — the ordered roadmap of Minors and Patches — applying a quality bar (tiny independently-testable steps, dependency ordering, risk tags, right-sizing) and leaving numbering room so future work can append near its theme. Hands off to phase-loop (multi-phase) or phase-tracker (single Minor).
awjackson2/phase-skills · ★ 0 · AI & Automation · score 70

Install: claude install-skill awjackson2/phase-skills

# Phase Decompose This skill produces the **umbrella plan** (`MAJOR.0.0`) that `phase-loop` consumes: an ordered roadmap that chunks a large goal into the smallest sensible Minors and Patches. Chunk quality is the single biggest determinant of whether a loop succeeds, so this skill exists to apply a real standard to the breakdown rather than improvising it inline. **Model tip (optional).** This skill is planning-only — a good candidate for a stronger-reasoning model (e.g. `/model opus`) for the whole session, since chunk quality is what determines whether the loop it feeds succeeds. It is **not a coding phase**. The umbrella it writes is a planning artifact (`MAJOR.0.0`), created on a `docs/<major>-umbrella` branch and merged to the default branch before looping — the same handling `phase-loop` describes. Terminology follows [TERMINOLOGY.md](../../../TERMINOLOGY.md). ## The quality bar A good roadmap satisfies all of these: - **Tiny and independently testable.** Each Minor is one shippable feature that can be implemented *and verified on its own*. If a Minor can't be tested without another unshipped Minor, it's mis-cut. - **Dependency-ordered.** Sequence so every phase builds only on already-shipped phases. Note each Minor's dependencies explicitly; if two are mutually dependent, they're really one Minor (or the seam is wrong). - **Vertical over horizontal where possible.** Prefer slices that deliver end-to-end value ("user can log in") over horizontal layers ("all the