What problem does it solve? Turning a plan, spec, or epic into actionable work items is error-prone: slices are too big, dependencies are unclear, and tracker publishing is manual. This Skill decomposes work into tracer-bullet vertical slices with explicit blocking edges, then publishes them to the configured tracker only after user approval. ## Core Features & Use Cases - Two-phase gated workflow: Drafts a ticket breakdown for review first, and publishes nothing until the user explicitly approves the decomposition. - Tracer-bullet slicing: Cuts narrow vertical slices across schema, API, UI, and tests, with expand-contract sequencing for wide refactors and human time estimates as a granularity signal. - Discovery Context propagation: Assigns approved file paths to each ticket, builds a filtered Repo Map, and runs one cheap-model advisory call to add exact dependency paths. - Tracker publishing: Writes local ticket files under .scratch/ or creates GitHub issues via gh issue create --body-file, linking them as native sub-issues with triage labels (workflow::ready, hitl/afk, task-report::required). - Use Case: After /to-spec publishes an epic, run this Skill to split it into 4-6 demoable tickets with blocking edges, review the breakdown, then publish them as labeled sub-issues ready for /implement. ## Quick Start Ask the agent to break the current spec or epic into tracer-bullet tickets with blocking edges and publish them to the configured tracker after your approval.
