Verified:GitHub

create-epics

Name: create-epics
Availability: InStock
Author: xganqaq

Convert approved GDDs and architecture ownership into bounded epic definitions with traced requirements and ADR coverage.

1|Updated May 5, 2026

Search Tags:#architecture #project planning #claude code #epics #requirements management #gdd #adr traceability

Ready to run

npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill create-epics-xganqaq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/create-epics
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill create-epics-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents chaotic implementation by translating approved GDDs and architecture into bounded epic plans with clear ownership, governing ADRs, and traceability to requirements.

Core Features & Use Cases

Layered epic generation: Create one epic per architectural module, respecting foundation→core→feature→presentation dependency order.
Requirement tracing & ADR gating: Uses the TR registry to identify traced vs untraced requirements and warns when ADRs are missing coverage.
Review-mode guardrails: Supports review modes (full/lean/solo) that control whether an epic structure gate is spawned before writing files.
Collaborative studio protocol: Presents each epic for approval before writing, then updates the epic index for downstream story creation.

Quick Start

Run /create-epics layer: core --review lean to generate core epics from in-scope GDDs with lean gating.

Frequently Asked Questions about create-epics

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

FAQPage Schema

How do I convert an approved GDD into epic-sized build plans?▼

You generate bounded epic definitions by parsing summary sections to scope inputs, loading architecture and ADR registry data, and producing EPIC.md files plus an epic index for a specific development layer.

What is epic generation in project planning and how does it handle requirement tracing?▼

Epic generation translates approved GDDs into bounded plans while using the TR registry to identify traced versus untraced requirements, warning you when ADRs are missing coverage for those requirements.

Can I generate epics for a specific architectural layer like core or presentation?▼

Yes, you can run the skill for a targeted development layer like core, generating one epic per architectural module while respecting the foundation, core, feature, and presentation dependency order.

Do I need to run architecture review and control manifest before creating epics?▼

Yes, you need approved GDDs and architecture module ownership from control-manifest and architecture-review as prerequisites during pre-production planning to prepare the next step of story breakdown.

How do review modes control the epic creation workflow?▼

Review modes like full, lean, or solo control whether an epic structure gate is spawned for approval before writing production files, ensuring collaborative studio protocol without creating stories.

Why does epic generation warn about missing ADR coverage?▼

Epic generation warns about missing ADR coverage because it enforces traceability to requirements, ensuring every bounded epic plan has clear ownership and governing architecture decision records to prevent chaotic implementation.