git:20260507.8dfdcb4 to git:20260507.9f5be95

---

name: story-decomposition

description: Break technical specifications into small, implementable stories with dependency ordering

allowed-tools: [Read, Write, Edit, Bash, Grep, Glob]

graph:

domains: [domain:software-engineering]

skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop]

workflows: [workflow:feature-development]

topics: [topic:developer-experience]

roles: [role:tech-lead, role:backend-engineer]

# 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.js` Phase 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