create-epics

Create epics from GDDs and architecture documentation for game-server backend modules.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/nguyennd93/game_server_studio --skill create-epics-nguyennd93
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/nguyennd93/game_server_studio/tree/main/.claude/skills/create-epics
Command: npx skills add https://github.com/nguyennd93/game_server_studio --skill create-epics-nguyennd93

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a structured and organized approach to creating epics for game-server backend development, ensuring comprehensive coverage of all architectural modules and related requirements.

Core Features & Use Cases

  • Epic Creation: Automatically translates approved Game Design Documents (GDDs) and architecture into defined epics for each architectural module.
  • Scope Definition: Defines the scope, governing Architecture Decision Records (ADRs), runtime and stack risks, and untraced requirements for each epic.
  • Layer Processing: Supports layer-wise processing to ensure dependency safety and proper sequencing.
  • Review Mode: Offers different review modes (full, lean, solo) to accommodate varying levels of review required for each epic.

Quick Start

Use the /create-epics command followed by the system or layer you want to create epics for, like: /create-epics layer: foundation

Frequently Asked Questions about create-epics

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

FAQPage Schema
How do I create epics for game-server backend development from a GDD?

To create epics for game-server backend development, this Skill maps approved Game Design Documents and architecture modules to their respective epics, defining scope and governing ADRs. It automates translating architectural documentation into structured development epics.

How do I define scope and runtime risks for backend architectural epics?

Defining scope and runtime risks for backend architectural epics involves mapping untraced requirements and stack risks to each module. This Skill processes architecture documentation to outline governing ADRs and specific scope boundaries for every generated epic.

Can I process backend architecture epics layer by layer to ensure dependency safety?

Yes, you can process backend architecture epics layer by layer to ensure dependency safety. This Skill supports layer-wise processing, allowing you to sequence epic generation properly using commands like /create-epics layer: foundation.

What review modes are available when generating epics from architecture documentation?

Available review modes for generating epics from architecture documentation include full, lean, and solo. These modes accommodate varying levels of review required for each epic, ensuring flexible validation during backend development planning.

Do I need Architecture Decision Records to map backend modules to epics?

Yes, Architecture Decision Records (ADRs) are required to map backend modules to epics. This Skill uses ADRs alongside Game Design Documents to define the governing decisions, runtime risks, and scope for each architectural epic.