What problem does it solve? Turning a plan, spec, or conversation into an actionable set of tickets is slow and error-prone: slices get too big, dependencies get missed, and premature tracker entries create noise. This Skill produces a reviewable, dependency-aware ticket breakdown as a draft only, so teams can validate scope and sequencing before anything is published. ## Core Features & Use Cases - Tracer-bullet slicing: Splits work into the smallest complete vertical slices, each with end-to-end behavior, independently verifiable acceptance criteria, and a suggested execution order. - Dependency validation: Assigns stable local identifiers, checks that every dependency exists, and verifies the execution order contains no cycles. - Draft-only boundary: Never calls an issue tracker or creates labels, links, or files; publication is treated as a separate, explicitly authorized task. - Use Case: After agreeing on a feature plan in conversation, ask for a ticket breakdown and receive a numbered Markdown list of review-ready tickets with blockers and proof requirements, ready for team review before anything is created in a tracker. ## Quick Start Use the draft-tickets skill to break the current plan into review-ready tracer-bullet tickets without publishing them.
