create-epics

Generate epics from CDDs and architecture artifacts with ADR alignment and requirement tracing.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill create-epics-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/create-epics
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill create-epics-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product and technical leads convert approved CDDs and architecture documentation into well-scoped epics, so planning starts from governed system boundaries instead of vague initiative names.

Core Features & Use Cases

  • Epic Scoping: Break a system into one epic per architectural module and layer.
  • Governance Alignment: Tie each epic to the relevant ADRs and surface technology risk.
  • Requirement Traceability: Identify uncovered requirements before stories are created.
  • Use Case: A lead preparing a release can turn approved design and architecture inputs into an epic summary that is ready for story breakdown and review.

Quick Start

Ask the skill to create epics for a specific layer or system using the approved architecture and CDD sources in the repository.

Frequently Asked Questions about create-epics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert approved architecture and CDD documents into epics?

Epic scoping from approved CDDs applies layer-by-layer breakdown to generate one epic per architectural module. It reads CDD summaries and architecture boundaries to produce review-ready epic metadata for product planning.

What is requirement traceability in epic scoping and why does it matter?

Requirement traceability in epic scoping identifies uncovered requirements before stories are created. It uses TR registry entries to map requirements against epics, generating untraced requirement warnings so teams avoid gaps during release planning.

How do I align epics with ADRs during product planning?

To align epics with ADRs, tie each generated epic to relevant ADR coverage. This governance alignment step surfaces technology risks and ensures epic scoping respects approved architectural decision records.

Can I create epics for a specific architectural layer instead of the whole system?

Yes, epic scoping supports targeting specific architectural layers. You can generate epics for a single layer by reading the approved architecture boundaries and CDD sources available in the product repository.

What happens to requirements that are not covered by the generated epics?

Requirements not covered by generated epics trigger untraced requirement warnings. The skill checks TR registry entries against scoped epics to surface uncovered requirements before any story breakdown begins.

Do I need approved CDDs before generating epics from architecture artifacts?

Yes, approved CDDs are required before generating epics. The skill reads CDD summaries, architecture boundaries, and ADR coverage to ensure planning starts from governed system boundaries rather than vague initiative names.