skills.rest
rakhnianskii9
rakhnianskii9COMMUNITY
Explore all skills by this author →
GitHub

create-epics

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

Updated Apr 24, 2026
Search Tags:#architecture#adr#epics#godot#project-management#gdd
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill create-epics-rakhnianskii9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/create-epics
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill create-epics-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate approved GDDs and architecture into epics that map to individual architectural modules, ensuring traceability from design decisions to implementation and enabling governance oversight.

Core Features & Use Cases

  • Create one epic per architectural module, embedding scope and architectural ownership.
  • Capture governing ADRs, engine risk, and untraced requirements to surface governance gaps early.
  • Do not generate stories — use /create-stories after each epic to plan implementation.

Quick Start

Run the epic creation flow for a chosen layer or system to begin generating architecture-aligned epics.

Frequently Asked Questions about create-epics

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

FAQPage Schema
How do I translate a game design document into actionable epics?▼

The Skill maps approved game design documents and architecture into actionable epics, creating one epic per architectural module with defined scope and governing ADRs.

How are architecture decisions and engine risks captured during epic creation?▼

Epic creation captures governing ADRs, engine risk, and untraced requirements directly within each architectural module's epic to surface governance gaps early in the project lifecycle.

Does epic generation break down architectural modules into user stories?▼

Epic generation does not break modules into user stories. It strictly defines epic scope and architectural ownership, requiring a separate /create-stories [epic-slug] command to plan implementation stories afterward.

What is the best way to ensure traceability from design decisions to game implementation?▼

Ensuring traceability from design to implementation requires generating architecture-aligned epics that embed architectural ownership and governing ADRs directly from the approved GDD.

Can I use this epic creation flow for Godot project management?▼

Yes, the epic creation flow supports Godot project management by translating approved GDDs and architecture into actionable epics while specifically capturing engine risk for the Godot platform.

Related Skills

Explore More Software Engineering Skills→
sumilee-pcusumilee-pcu

create-epics

Translate game design documents into bounded architectural epics with ADRs and engine risks.

Community
Advanced
solace-illsolace-ill

create-epics

Translate approved GDDs and architecture into epics per architectural module.

Community
Advanced
WindXRanWindXRan

create-stories

Convert an epic and GDD acceptance criteria into traceable story markdown files.

Community
Advanced
HechaoYannetHechaoYannet

create-epics

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

Community
Advanced