What problem does it solve? Turning a feature or project into well-scoped Jira tickets is slow and error-prone: tickets end up too big, vaguely described, missing acceptance criteria, or disconnected from related work. This Skill structures the entire ticket-writing workflow so every ticket is independently deliverable and understandable by a teammate with zero conversation context. ## Core Features & Use Cases - Work Decomposition: Slices features and epics into right-sized, vertically-cut tickets (roughly one PR each), with spike tickets for blocking unknowns. - Structured Ticket Creation: Drafts summaries and markdown descriptions (Why, What, Out of scope, Acceptance criteria, References), gets your approval, then creates tickets with jira-cli using -T body files to avoid shell-quoting issues. - Issue Linking: Establishes parent/epic membership, Blocks ordering between siblings, and Relates links back to origin tickets. - Use Case: You describe a new webhook feature; the Skill breaks it into an epic with three child tasks, drafts each description with checkable acceptance criteria, confirms the plan with you, then creates and links everything in Jira. ## Quick Start Break this feature down into Jira tickets and create them with jira-cli after I approve the drafts.
