← ClaudeAtlas

executinglisted

Runs a written plan task by task with checks and a final review. Use when a plan exists and the user says go, implement it, execute the plan, or build the planned feature. Not for writing plans, single edits or reviews.
t8jwscc7qy-sketch/foma-skills · ★ 2 · AI & Automation · score 78
Install: claude install-skill t8jwscc7qy-sketch/foma-skills
Execute `docs/plans/<feature>/plan.md` task by task, verify each result yourself, review the whole feature once, and close the plan. Uses: foma-skills:tdd (test-first tasks), foma-skills:debugging (a failure you don't understand), foma-skills:reviewing (final pass), foma-skills:committing (commit rule), foma-skills:documenting (decisions found); agents `implementer`, `reviewer`, `explorer` (wide code search). ## Steps 1. Find the plan: `## Where things live` in CLAUDE.md, else `docs/plans/<feature>/plan.md`. None: say so and point to foma-skills:planning, or do it directly if the change is small. Read the plan once. Resume at the first task whose Status is not `done`. `Started:` empty → set it to now (`date '+%F %H:%M'`). 2. Choose the path and say it in one line: 1–2 tasks → inline, you do them; more → one `implementer` agent per task, run one at a time. 3. Appetite check before each task (plan has `Appetite:`): time since `Started:` plus the work left clearly past the budget → stop, say how far over and offer the `cut first` item; the user picks. Cut: mark that item cut in the plan and go on. Extend: ask the new budget, replace `Appetite:` and reset `Started:` to now. Continue: append `— continue ok` to `Appetite:`. A plan whose `Appetite:` ends with `continue ok` is not checked again. 4. Per task: set `Status: doing` in the plan, then run it. - Inline: follow Steps, test-first where the task says so. - Agent: call the `implementer` agent with the Agent `model` para