create-epics

Translate approved GDDs and ADR inputs into bounded epics mapped to architectural modules.

Updated May 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill create-epics-francisvarga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/create-epics
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill create-epics-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts approved design inputs (GDDs plus architecture and ADR context) into clear, bounded epic scopes per architectural module so your team can move forward without unclear ownership or missing requirement coverage.

Core Features & Use Cases

  • Epic scoping from architecture: maps each system to the correct architectural module, defining what must be built without prescribing implementation steps.
  • Governing ADR alignment: selects the governing ADRs, summarizes engine risk from those ADRs, and surfaces which requirements are covered.
  • Requirement tracing guardrails: warns about untraced requirements (TR-IDs without Accepted ADRs) and blocks only at the stories stage, not at epic creation.
  • Controlled workflow by layer and system: supports layer-by-layer processing (foundation/core/feature/presentation) or single-system runs, with review-mode gating to prevent unrealistic plans.

Quick Start

Run create-epics for Core only using: /create-epics layer: core --review lean.

Frequently Asked Questions about create-epics

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

FAQPage Schema
How do I turn a GDD into epics mapped to architectural modules?

You turn a GDD into epics by translating approved design, architecture, and ADR inputs into bounded epic scopes mapped to specific architectural modules. This structures production work without prescribing implementation steps.

How does requirement tracing work when generating epics from a GDD?

Requirement tracing uses a TR registry to detect untraced requirements lacking Accepted ADRs. It warns about missing requirement coverage during epic creation but only blocks progress at the stories stage.

Can I generate epics for just the core layer of my game architecture?

Yes, you can generate epics for a single layer like core by running a targeted workflow. The tool supports layer-by-layer processing in foundation, core, feature, and presentation ordering.

What is the role of ADRs in game production planning and epic scoping?

ADRs govern epic scoping by selecting governing decisions, summarizing engine risk, and surfacing requirement coverage before any file writes. They ensure epics align with approved architectural decisions.

What files are produced when scoping game production epics?

Epic scoping produces an EPIC.md file inside a production/epics/[epic-slug]/ directory and an index.md file. These outputs provide deterministic epic content generation for production planning.

When should I use review mode for epic creation in game production?

Use review mode during epic creation to enforce gating that prevents unrealistic production plans. Lean review mode validates layer and system scope before proceeding to further file writes.