← ClaudeAtlas

planlisted

Turn .fabrika/work/spec.md into an ordered implementation plan at .fabrika/work/plan.md — vertical slices, each a test and the code that passes it — then grill it. Use after the spec, before implementing.
perkzen/fabrika · ★ 1 · AI & Automation · score 53
Install: claude install-skill perkzen/fabrika
# Plan Produce the plan another session will execute: concrete, ordered, and already stress-tested. ## Process 1. **Read** `.fabrika/work/spec.md`. Explore the code the spec touches until you can name the files and functions involved and the prior-art tests the new ones will resemble. 2. **Write** `.fabrika/work/plan.md` from the template below. The first slice is the **tracer bullet**: the thinnest end-to-end path through every layer the feature touches. Every later slice adds one behaviour. Size the plan to the change: a one-file fix is a one-slice plan, and a section with nothing real in it — no risk worth naming, no second file — is a heading and nothing else. The next session reads this cold, so what it needs is every file and seam named, not volume. 3. **Grill** the plan with the `fabrika:grill-with-docs` skill. It fills `## Decisions`; fold what it settles back into Goal, Slices, and Files. 4. **Done** when every slice names a test, a seam from the spec, and the code that passes it; every risk has a mitigation or a recorded acceptance; and the grill's frontier is empty. Beyond the plan and what `fabrika:domain-modeling` wrote, change no other file. <plan-template> # Plan: <ticket id> ## Goal One paragraph restating the goal in your own words. ## Slices Ordered vertical slices, each one red→green cycle at a seam from the spec: 1. **<test name>** — asserts <behaviour>. Seam: <seam>. Makes it pass: <file/function created or changed, one line each>. ## Fi