OpenParable
Skip to content
← Back to skills

Story Decomposition

Productivity
story-decomposition

Story Decomposition is an Agent Skill for productivity published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Break technical specifications into small, implementable stories with dependency ordering

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/methodologies/maestro/skills/story-decomposition/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/story-decomposition, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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