Documentation
README
To Tickets
Break a plan, spec, or conversation into a set of tickets — tracer-bullet vertical slices, each declaring the tickets that block it.
Process
1. Gather context
Work from whatever is already in the conversation context. If the user passes a reference (a spec path such as .plan/<slug>/spec.md, or any other document) as an argument, fetch it and read it in full.
2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand the current state of the code. If a CONTEXT.md glossary exists at the repo root, ticket titles and descriptions should use its vocabulary; respect ADRs in docs/adr/ in the area you're touching. If neither exists, proceed silently.
This is the opening of the README. Read the full README on GitHub.