Babysitter story-decomposition

Break technical specifications into small, implementable stories with dependency ordering

install

source · Clone the upstream repo

git clone https://github.com/a5c-ai/babysitter

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/methodologies/maestro/skills/story-decomposition" ~/.claude/skills/a5c-ai-babysitter-story-decomposition && rm -rf "$T"

manifest: library/methodologies/maestro/skills/story-decomposition/SKILL.md

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