What does Epic Generation produce?

An epic document that includes architecture decisions (ADRs), a dependency graph, and a validation report to ensure PRD coverage.

What inputs are required?

projectName, featureName, prd, and optionally existingCodebase for brownfield assessment.

When should I use this skill?

When turning a finalized PRD into an actionable technical plan with architecture decisions and cross-team dependencies.

Epic Generation

npx machina-cli add skill a5c-ai/babysitter/epic-generation --openclaw

Files (1)

SKILL.md

911 B

Epic Generation

Transform PRD into a technical implementation plan with architecture decisions and dependency mapping.

Agent

Architect - architect

Workflow

Parse PRD and extract structured requirements
Define architecture decisions with ADR format
Specify technology approach and stack choices
Map internal, external, and cross-team dependencies
Assemble complete epic document
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

Source

git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/ccpm/skills/epic-generation/SKILL.md

View on GitHub

Overview

Epic Generation converts a finalized PRD into a detailed technical implementation plan. It produces architecture decisions in ADR format, a dependency graph, and a complete epic document to guide cross-team delivery. This helps ensure every PRD requirement is covered and auditable.

How This Skill Works

The skill parses the PRD to extract structured requirements, defines architecture decisions using ADRs, specifies tech approach and stack choices, maps internal/external/cross-team dependencies, assembles a complete epic document, and validates that the epic covers all PRD requirements.

When to Use It

Starting a new feature directly from a finalized PRD and needing an actionable implementation plan
Brownfield projects where existingCodebase needs mapping to a new epic and dependencies
Coordinating cross-team work with a dependency graph and ADRs for governance
Ensuring architecture decisions are well-documented (ADR) before implementation
Generating a validation report to confirm PRD coverage before development begins

Quick Start

Step 1: Provide inputs - projectName, featureName, prd, and optional existingCodebase
Step 2: Run the Epic Generation workflow to produce an epic document, ADRs, and a dependency graph
Step 3: Review, then finalize the epic for implementation with the validation report

Best Practices

Extract and preserve traceable PRD requirements in the epic
Document Architecture Decisions with clear rationale and alternatives
Maintain an up-to-date dependency graph including internal and external deps
Produce and review a validation report validating PRD coverage
Version-control all epic artifacts (epic doc, ADRs, graph)

Example Use Cases

Epic for migrating a monolith to a microservices-based architecture with ADRs and a dependency graph
Epic planning for a customer onboarding feature with cross-team integrations
Brownfield enhancement: mapping PRD to an existing codebase and updating ADRs
Analytics platform overhaul planned from a PRD with external data dependencies
New security-focused feature implemented with ADR-driven architecture decisions

Frequently Asked Questions

Add this skill to your agents