Decompose to issues
Skill wakqasahmed/ai-engineering-workflow-skills/skills/engineering/decompose-to-issues
Canonical AI engineering workflow skills, aggregated by wakqasahmed/skills
npx -y skills add wakqasahmed/ai-engineering-workflow-skills --skill decompose-to-issuesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Break high-level work into independently executable GitHub issues using vertical slices. Use when a plan, PRD, roadmap item, or vague feature needs issue-sized execution units.
SKILL.md
1.1 KB, as published. Nobody here has run it
Decompose To Issues
Use decomposition as context control, not project-management ceremony.
Workflow
- Identify the user-visible or operational outcome.
- Split by vertical slices that can be implemented, reviewed, and verified independently.
- Put shared setup before dependent slices only when it unlocks multiple issues.
- Mark dependencies explicitly.
- Keep each issue small enough for a fresh agent to complete in one focused pass when possible.
Issue Shape
Each issue should include:
- Problem
- Acceptance criteria
- Verification plan
- Expected test layers
- Constraints / non-goals
- Links and relevant files
- Risk level
Guardrails
- Avoid horizontal slices like "build backend" and "build frontend" unless the architecture truly requires it.
- Do not create issues that require inherited conversation context to understand.
- Create follow-up issues for scope discovered during implementation.