tickets

# Tickets Break a plan, spec, or conversation into **tickets** — tracer-bullet vertical slices, each declaring the tickets that **block** it, written as markdown files alongside the spec. ## Process ### 1. Gather context Work from whatever is already in the conversation context. If the user passes a spec path (usually `docs/specs/<feature>.md`), read it in full. ### 2. Explore the codebase If you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain vocabulary. Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change." ### 3. Draft vertical slices Break the work into **tracer bullet** tickets. <vertical-slice-rules> - Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer - A completed slice is demoable or verifiable on its own - Each slice is sized to fit in a single fresh context window — one ticket, one `/implement` run - Any prefactoring should be done first </vertical-slice-rules> Give each ticket its **blocking edges** — the other tickets that must complete before it can start. A ticket with no blockers can start immediately. **Wide refactors are the exception to vertical slicing.** A **wide refactor** is one mechanical change — rename a column, retype a shared symbol — whose **blast radius** fans across the...