breakdownlisted

# Breakdown The plan itself comes from Claude Code's built-in plan mode (engineering-principles §7). This skill breaks the result into tickets. Two modes. For work that fits one session, break it into **tracer-bullet tickets** with blocking edges. For work too large for one session, chart a **decision map** — a shared index of decision tickets resolved one at a time until the way to the destination is clear. ## When to use - You have an approved plan, spec, or conversation result to break into tickets. - The work spans multiple sessions and needs a shared decision map. - You need to sequence work by blocking edges before implementation starts. **Not for:** Work that fits one session (just `implement` it); writing the spec itself (use `spec`). ## Steps ### Mode 1 — Tracer-bullet tickets (work fits one session) 1. **Gather context.** Read the plan or spec. If the user passes a reference (path, issue number, URL), fetch its full body. Explore the codebase if you haven't, so ticket titles use the project's domain glossary and respect existing ADRs. 2. **Draft vertical slices.** Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, not a horizontal layer. A completed slice is demoable on its own. Size each to a single fresh context. 3. **Declare blocking edges.** For each ticket, list the tickets that must complete before it can start. A ticket with no blockers starts immediately. 4. **Wide-refactor excepti