create-epics

Convert approved GDDs and architecture docs into scoped epics with ADRs.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill create-epics-hechaoyannet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/create-epics
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill create-epics-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts approved design documents and architecture guidance into clearly scoped epics for architectural modules, ensuring governance, traceability, and alignment with engineering plans.

Core Features & Use Cases

  • Epic per module: Creates a named epic for each architectural module with defined scope, ADRs, and engine risk.
  • Governance & traceability: Captures governing ADRs and tracks untraced requirements to surface gaps.
  • No stories yet: Deliberately does not break epics into stories; use /create-stories after each epic is created.
  • Output artifacts: Generates production/epics/[epic-slug]/EPIC.md and updates production/epics/index.md.

Quick Start

Provide the current GDDs and architecture context to generate epics for in-scope systems.

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 GDDs into architectural epics for project modules?

To translate GDDs into architectural epics, provide approved design documents and architecture context to generate a named epic per module. This captures governing ADRs and tracks untraced requirements across Foundation, Core, Feature, and Presentation layers.

How do I track governing ADRs and untraced requirements when creating epics?

Tracking governing ADRs and untraced requirements during epic creation ensures architectural governance and traceability. The process surfaces requirement gaps by mapping approved architecture docs directly into scoped epics for all in-scope systems.

What is the best way to structure architectural epics across Foundation, Core, Feature, and Presentation layers?

Structuring architectural epics across all project layers involves creating a named epic for each architectural module. This ensures epics capture engine risk and defined scope without prematurely breaking down into user stories.

Do I need to break architectural epics into stories immediately after generation?

Breaking architectural epics into stories immediately is not required. Epics are deliberately generated without story breakdowns to maintain architectural focus; use dedicated story creation steps after each epic is fully established.

Can I generate architectural epics if my design documents only cover specific in-scope systems?

Generating architectural epics for specific in-scope systems is fully supported. Provide the current GDDs and architecture context for those systems, and the process will output scoped epics capturing engine risk and governing ADRs.

What output artifacts are generated when converting architecture docs into epics?

Converting architecture docs into epics generates EPIC.md files within production/epics/[epic-slug]/ directories and updates the production/epics/index.md file to index the newly created architectural modules.