← ClaudeAtlas

planninglisted

Breaks a feature into ordered, verifiable tasks in a plan file and assigns a model per task. Use when the user asks for a plan, a task breakdown, or which model fits a plan task, or a change spans several files. Not for small edits or reviews.
t8jwscc7qy-sketch/foma-skills · ★ 2 · AI & Automation · score 78
Install: claude install-skill t8jwscc7qy-sketch/foma-skills
Size the work, then write a short plan of vertical, independently verifiable tasks that the user approves before anything is built. Uses: foma-skills:documenting (decisions found while planning). ## Steps 1. Pick the path and say it in one line. - Small, clear change (1-2 files, no design choice): say "small change, doing it directly" and stop. No plan. - Feature: look for a spec (`docs/specs/<name>.md` or the spec line in `## Where things live`). None and the idea is fuzzy: suggest `/foma-skills:shaping` and stop. - Multi-step work: continue. 2. Read the CLAUDE.md contract (`## Commands`, `## Where things live`, conventions), then grep for the code the plan touches and read only the relevant ranges. Note the test command and existing patterns. 3. If the spec spans independent subsystems, propose one plan each. If a wide mechanical change (rename, retype) breaks many call sites at once, sequence it expand, migrate in batches, contract. 4. Draft tasks as vertical slices: each cuts through every layer it needs, is demoable or checkable alone, fits one fresh context, and comes in dependency order. Do prefactoring first. Fold setup, config and docs into the task that needs them; split only where a reviewer could reject one task and accept its neighbour. 5. Fill each task: real files, steps with one checkable action each, `Done when` with the project's command, `Status: todo`. Set `Model:` and effort per task (`references/routing.md`). 6. Self-check: every spec requirem