epic-generation
The epic-generation skill converts product requirement documents into detailed technical implementation plans by parsing requirements, documenting architecture decisions using ADR format, specifying technology choices, and mapping internal, external, and cross-team dependencies. Use this when transitioning from product planning to technical execution to ensure architectural alignment and dependency clarity across engineering teams.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/epic-generation && cp -r /tmp/epic-generation/library/methodologies/ccpm/skills/epic-generation ~/.claude/skills/epic-generationSKILL.md
# Epic Generation Transform PRD into a technical implementation plan with architecture decisions and dependency mapping. ## Agent Architect - `architect` ## Workflow 1. Parse PRD and extract structured requirements 2. Define architecture decisions with ADR format 3. Specify technology approach and stack choices 4. Map internal, external, and cross-team dependencies 5. Assemble complete epic document 6. Validate epic covers all PRD requirements ## Inputs - `projectName` - Project name - `featureName` - Feature identifier - `prd` - Finalized PRD from Phase 1 - `existingCodebase` - Codebase analysis for brownfield (optional) ## Outputs - Epic document with architecture, tech approach, dependencies - Architecture Decision Records (ADRs) - Dependency graph - Validation report ## Process Files - `ccpm-epic-planning.js` - Standalone epic planning - `ccpm-orchestrator.js` - Phase 2 of full lifecycle
Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement