← ClaudeAtlas

astra-to-ticketslisted

Cut a committed spec into tracer-bullet tickets a Builder can take one per session: vertical slices with prerequisite edges, published to the project's tracker in build order. A ticket that changes a surface carries Glance, States and Criteria; every ticket carries its quick/full label. Shaper's Tickets phase; opens on Thomas's release line.
thientranhung/astragentic · ★ 4 · Code & Development · score 73
Install: claude install-skill thientranhung/astragentic
# To tickets Thomas's release line is `/astra-to-tickets <spec-id>`. Cut from the spec as committed after the arm. ## 1. Gather - The spec: full body and comments, and the spec-stage findings; a ticket that ignores a finding is how a finding gets waved through. - The PRD (`docs/prd.md` or the project's own) for **actor names and FR ids**. Actors live there, once; a ticket uses the PRD's name verbatim, never a synonym. - `docs/qa/plan-<slug>.md` from `test-design`: cut along the slices the plan drew. - The code the spec touches: where deployment splits, which slices share files. Code that contradicts a spec line is a `Source conflict:` note, never silently resolved. Glossary vocabulary; respect ADRs. ## 2. Slice Each ticket is a **tracer bullet**: a narrow but complete path through every layer the work touches (schema, API, UI, tests), verifiable on its own, sized for **one Builder session in one fresh context window**. A horizontal slice (one layer, no behaviour) is not a ticket. - **Prefactoring first**: make the change easy, then make the easy change. An opening refactor is its own ticket when code quality calls for one. - **Tracer bullet first, then the slice the spec is least sure of.** Risk is retired early. - **Tickets touching the same code form one ordered lane**; an interface two lanes share gets a stub as its own early ticket so neither lane waits on the other. - **Split, never shrink**: "for now", "placeholder", "simplified", "wired later" is a se