Turn approved scope into concise, independently verifiable ticket drafts.
- Read the source plan and identify outcomes, dependencies, and constraints.
- Split only where work can be implemented and verified independently.
- Give each draft a title, context, acceptance criteria, dependencies, and technical notes.
- Suggest estimates or labels only when the project defines that policy; never invent sprint buckets, title prefixes, owners, or status transitions.
- Return the drafts in Markdown, in dependency order. Leave tracker records unchanged.
For GitHub issue creation or edits, use github-issue with the user's explicit request.