skills.rest
Negentropy-Laby
Negentropy-LabyOFFICIAL
Explore all skills by this author →
GitHub

create-epics

Translate approved CDDs and architecture into epics mapped to architectural modules.

3|Updated Jun 3, 2026
Search Tags:#automation#architecture#scoping#adr#epics#cdd#project-management
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill create-epics-negentropy-laby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/create-epics
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill create-epics-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate approved CDDs and architecture into epics mapped to architectural modules. This ensures each module has a clear governance scope and traceability to ADRs and architecture decisions.

Core Features & Use Cases

  • One epic per architectural module with governing ADRs and technology risk previews.
  • Outputs: production/epics/[epic-slug]/EPIC.md and production/epics/index.md.
  • Next steps: run /create-stories [epic-slug] to break epics into stories.

Quick Start

Run /create-epics all or /create-epics layer: core to generate epics and preview ADR coverage before writing.

Frequently Asked Questions about create-epics

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

FAQPage Schema
How do I translate approved CDDs and architecture into epics mapped to modules?▼

To translate approved CDDs into epics, generate one epic per architectural module with governing ADRs and technology risk previews. Apply this across Foundation, Core, Feature, and Presentation layers to ensure clear governance scope and architectural traceability.

What is the best way to structure epics for downstream story creation?▼

The best way to structure epics for story creation is to output organized files like production/epics/[epic-slug]/EPIC.md and production/epics/index.md. This standardizes epic templates and ADR coverage for downstream processing.

Do I need approved architecture decisions before generating project epics?▼

Yes, you need approved CDDs and architecture decisions before generating epics. The process relies on mapping these approved decisions to architectural modules to produce governing ADRs and technology risk previews for review.

How do I generate epics for a specific architectural layer like Core or Foundation?▼

To generate epics for a specific architectural layer, run commands like /create-epics layer: core. This targets the specified layer to produce the relevant governing ADRs and epic files needed for review before creating stories.

Can I break generated epics into actionable development stories?▼

Yes, you can break generated epics into actionable stories by running /create-stories [epic-slug] after generating the epics. This step follows the initial epic creation and ADR coverage preview.

Why preview ADR coverage before writing stories from epics?▼

Previewing ADR coverage before writing stories ensures each architectural module has clear governance scope and traceability to architecture decisions. It allows you to review technology risks and governing ADRs prior to detailed story creation.

Related Skills

Explore More Software Engineering Skills→
kay6198835kay6198835

create-epics

Transform approved GDDs and architecture guidance into epics per architectural module.

Community
Advanced
adolfoaranaes12adolfoaranaes12
2

breakdown-epic

Break down epics into user stories with acceptance criteria and sprint groupings.

Community
Advanced
MarkusonMarkuson

bmad-sprint-planning

Parse epic and story markdown to generate sprint-status.yaml tracking files.

Community
Advanced
wsmanwsman
18

create-epics

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

Community
Advanced