to-tickets-plus
To Tickets Plus
Break a plan, spec, or conversation into tickets — tracer-bullet vertical slices, each declaring the tickets that block it.
Pipeline position: to-spec-plus (record) → to-tickets-plus (slice) → implement-plus (build one ticket per session).
Process
1. Gather context
Work from whatever is already in the conversation. If the user passes a reference (a spec path, an issue id or URL), fetch it and read its full body and comments.
2. Explore the codebase
If you haven't already, explore to understand the current state. Ticket titles and descriptions use the project's domain vocabulary (CONTEXT.md/glossary if present) and respect ADRs in the area.
Look for opportunities to prefactor — restructure first so the feature lands cleanly. "Make the change easy, then make the easy change." Prefactors become the first tickets.