create-epics

Translate approved GDDs and architecture into epics per architectural module.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill create-epics-thilthpc01208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/thilthpc01208/Codex-Game-Studios/tree/main/.codex/skills/create-epics
Command: npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill create-epics-thilthpc01208

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates approved GDDs and architecture into epics for architectural modules, defining scope, governing ADRs, engine risk, and untraced requirements.

Core Features & Use Cases

  • Maps each system to an architectural module and assigns governance ADRs.
  • Validates ADR coverage and flags untraced requirements for visibility.
  • Produces epic templates and an index to drive downstream epic creation and story planning.

Quick Start

Identify the target systems, review ADR coverage, approve epics one by one, then proceed to write epic files after gating.

Frequently Asked Questions about create-epics

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

FAQPage Schema
How do I turn an approved Game Design Document into architecture epics?

To turn an approved Game Design Document (GDD) into architecture epics, you translate it into structured epics mapped to architectural modules. This process scopes epics across Foundation, Core, Feature, and Presentation layers while validating ADR coverage and flagging untraced requirements before writing.

What is the best way to scope epics across architectural layers?

The best way to scope epics across architectural layers is to organize them in systems-index order across Foundation, Core, Feature, and Presentation layers. This ensures each epic corresponds to a specific architectural module and references relevant governance ADRs.

How do I validate ADR coverage before writing epic templates?

To validate ADR coverage before writing epic templates, you review the mapped architectural modules against existing Architecture Decision Records (ADRs). This process flags untraced requirements and ensures governance gates are referenced prior to epic approval.

Can I generate a production-ready epic index from an existing architecture?

Yes, you can generate a production-ready epic index from an existing architecture. The process produces an index that drives downstream epic creation and story planning by mapping systems to architectural modules and assigning governance ADRs.

Why do I need to surface untraced requirements during epic creation?

You need to surface untraced requirements during epic creation to maintain architectural visibility and prevent scope gaps. Flagging these requirements ensures that all GDD elements are accounted for before approving epic templates and proceeding to story planning.