story-decomposition
// Break technical specifications into small, implementable stories with dependency ordering
$ git log --oneline --stat
stars:384
forks:73
updated:March 4, 2026
SKILL.mdreadonly
SKILL.md Frontmatter
namestory-decomposition
descriptionBreak technical specifications into small, implementable stories with dependency ordering
allowed-toolsRead,Write,Edit,Bash,Grep,Glob
Story Decomposition
Capabilities
Breaks technical specifications into small, independently implementable stories. Establishes dependency ordering, estimates effort, and creates a dispatching queue for parallel coder execution.
Tool Use Instructions
- Use Read to examine the technical specification and existing code
- Use Grep/Glob to find existing modules and interfaces that stories will touch
- Use Write to generate story definitions
- Use Edit to refine stories based on feedback
Process Integration
- Used in
maestro-orchestrator.jsPhase 3 (Story Decomposition) - Used in
maestro-development.js(Story Prioritization) - Maps to tasks:
maestro-architect-story-decomp,maestro-dev-prioritize - Agent: Architect
- Each story should be completable by a single coder in one batch
- Outputs feed into parallel coder dispatch