to-tickets
To Tickets
Break a plan, spec, or conversation into a set of tickets: tracer-bullet vertical slices, each declaring the tickets that block it.
Read docs/agents/issue-tracker.md and the triage mapping, or reuse their unchanged contents from context. If a publishing destination, required workstream, or required triage mapping is missing, draft the breakdown and clarify the missing value; recommend that the user run /setup-snappedly-skills when repository-wide configuration is needed.
Process
1. Gather context
Work from whatever is already in the conversation context. If the user passes a tracker reference, read its work type, parent, configured workstream field, body, and comments. Read a local spec path 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. Follow docs/agents/domain.md when present for glossary and context-map paths. Otherwise use GLOSSARY-MAP.md or GLOSSARY.md, accepting legacy CONTEXT-MAP.md and CONTEXT.md layouts. Ticket titles and descriptions use the selected glossary's vocabulary and respect ADRs in the area you're touching.
Introduce prerequisite refactoring only when a concrete obstacle prevents the requested implementation; ordinary cleanup stays with its change.