work-items-breakdown
Installation
SKILL.md
Work items breakdown
Creating items in a shared tracker is visible to other people. Always show a preview and get a clear yes before you create anything.
1. Ask what the user needs
Ask these questions in one round (with recommended options first), unless the answers are already clear:
| Question | Typical options |
|---|---|
| Where do the items go? | GitHub issues (gh), GitLab issues (glab), Jira, Azure DevOps (az boards), Linear, a task list that the project keeps in git (the task file it already has, otherwise docs/<slug>-tasks.md) |
| What granularity? | One item per plan step (Recommended when a plan exists), one per acceptance criterion, one epic with child tasks |
| Which fields? | Labels, milestone, assignee, estimate, parent or epic, iteration |
| Do items link to each other? | Dependencies from the plan order, parent/child |
Check which tools are available (gh auth status, glab auth status, az account show, MCP servers). If none works, produce a markdown file and say how to import it.