Translate approved GDD systems into bounded epics aligned to architecture modules.
npx skills add https://github.com/WindXRan/y3td --skill create-epics-windxran
Please help me install this Agent Skill. Skill: create-epics Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/create-epics Command: npx skills add https://github.com/WindXRan/y3td --skill create-epics-windxran
Create-epics eliminates the ambiguity between game design docs (GDDs), architectural ownership, and engineering execution by translating approved design inputs into clearly bounded epics that are governed by accepted ADRs and validated against engine risk and requirement tracing.
Run create-epics with the specific scope you want, for example: create epics for the Core layer using lean review mode.
High-intent search queries and answers about installing and using this skill.
To translate GDDs into architecture-aligned epics, map each approved system to a bounded architectural module and record layer ownership. This ensures engineering execution directly reflects design inputs and architectural boundaries.
The correct layer order for generating epics is Foundation, then Core, then Feature, then Presentation. Running once per layer in this dependency-safe sequence prevents scope gaps and ensures foundational systems exist before building features.
ADRs trace requirements by loading authoritative system lists and architecture boundaries, then checking which TR requirements are traced versus untraced by accepted ADRs. The workflow warns you about untraced TRs to maintain requirement coverage.
Yes, you can generate epics for either a specific system or an entire architectural layer. Specifying a system scope filters the GDD summary to isolate in-scope requirements, ensuring targeted epic creation.
You need an approved GDD summary, an architecture definition, a control manifest, a TR registry, and an engine version input. Loading these inputs enables dependency-safe layer ordering and validates epics against engine risk.
No, the epic generation process never creates user stories. It strictly writes EPIC.md files and an epics index, leaving story creation as a separate downstream step to maintain clear scope boundaries.
MichaelSolatiGenerate an engine-validated master architecture document from game design documents.
Negentropy-LabyTranslate approved CDDs and architecture into epics mapped to architectural modules.
johnatas-henriqueDecompose game development epics into traceable stories with TR-IDs and acceptance criteria.
imgamerTranslate approved GDDs and architecture module ownership into one epic per module.
