Create GitHub Issue draft with AC/Non-goals/Tasks. Use when starting from vague requirements - asks clarifying questions if needed. Also used internally by create-issue skill.
Creates a well-structured GitHub Issue draft from vague user requirements.
Note: This skill is also used as part of the /create-issue workflow for learning purposes.
A short, actionable title (1 line).
Example:
Add snake_case to camelCase conversion function
Complete GitHub Issue body in this format:
## Problem / Why
[2-4 lines explaining the background and motivation]
## Acceptance Criteria
- [ ] [Observable outcome with example if possible]
- [ ] [Given/When/Then format preferred]
- [ ] [3-5 specific, testable criteria]
## Non-goals
- [What we explicitly won't do - 2-4 items]
## Constraints
- [Technical or business constraints - 1-3 items if applicable]
## Tasks
- [ ] Run /spec to create spec.md
- [ ] Run /plan to create plan.md
- [ ] Implement changes
- [ ] Run make test
- [ ] Create PR
User: "Add a function to convert text to camelCase"
Skill asks:
Then generates ISSUE_TITLE.txt and ISSUE_DRAFT.md.