skills.rest
cenconq25
cenconq25COMMUNITY
Explore all skills by this author →
GitHub

create-epics

Transform approved PRDs and architecture into Epic artifacts with TR-ID grouping.

39|6|Updated May 3, 2026
Search Tags:#planning#architecture#adr#epics#traceability#project-management#prds
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill create-epics-cenconq25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/create-epics
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill create-epics-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform approved PRDs and architecture into Epic artifacts that anchor downstream story creation and ensure traceability across the planning lifecycle.

Core Features & Use Cases

  • Group TR-IDs into epics per system, or create sub-epics when scope is large, to keep work organized.
  • Attach governing ADRs and control-manifest constraints to each epic to preserve governance and alignment.
  • Output: production/epics/<epic-slug>/EPIC.md for every epic, linking back to the PRD and ADR sources.

Quick Start

Run /create-epics to generate epics for all in-scope systems, or specify a system-name to scope to a single epic.

Frequently Asked Questions about create-epics

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

FAQPage Schema
How do I break down a PRD into epics for project management?▼

To break down a PRD into epics, group Technical Requirement IDs (TR-IDs) by system and align them with governing Architecture Decision Records (ADRs). This anchors downstream story creation and ensures traceability across the planning lifecycle.

What is epic traceability in software architecture planning?▼

Epic traceability is the mechanism linking generated epics back to approved PRDs, ADRs, and control manifest constraints. It preserves governance and alignment by recording these definitions in structured EPIC.md files.

When should I split a large PRD scope into multiple sub-epics?▼

You should split a large PRD scope into multiple sub-epics when the system scope is too large for a single epic. This keeps work organized and ensures each sub-epic properly anchors downstream story creation.

How do I generate epics for a specific system from an approved PRD?▼

To generate epics for a specific system from an approved PRD, execute the generation command and specify the system-name. This scopes the epic creation to a single system, outputting an EPIC.md file to the designated production directory.

Do I need ADRs and a control manifest to create epics?▼

Yes, you need ADRs and a control manifest to create epics with proper governance. Attaching these governing constraints to each epic preserves alignment and ensures the resulting EPIC.md files correctly reference the source PRD and ADR documentation.

Related Skills

Explore More Product & Management Skills→
adolfoaranaes12adolfoaranaes12
2

breakdown-epic

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

Community
Advanced
epieczkoepieczko

story.write

Convert decomposed epic items into formatted user story Markdown files.

Community
Intermediate
imgamerimgamer

create-epics

Translate approved GDDs and architecture module ownership into one epic per module.

Community
Advanced
ripabakripabak

breakdown-plan

Generate markdown project plans with dependency maps and GitHub issue checklists.

Community
Advanced