skills.rest
polsegu
polseguCOMMUNITY
Explore all skills by this author →
Website𝕏@Polsegu11GitHub

create-epics

Create one epic per architectural module from approved GDDs and architecture.

Updated Apr 10, 2026
Search Tags:#architecture#adr#epics#software-delivery#project-management#gdd
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill create-epics-polsegu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/create-epics
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill create-epics-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill translates approved GDDs and architectural decisions into epics, ensuring each architectural module is tracked as a discrete piece of work with defined ownership and governance.

Core Features & Use Cases

  • Epic per module: Creates one epic for each architectural module, capturing scope, ADR governance, engine risk, and untraced requirements.
  • Layered workflow: Processes epics in dependency-safe order across Foundation, Core, Feature, and Presentation layers.
  • Governance integration: References ADR coverage and TR requirements, surfacing untraced items for ADR planning.

Quick Start

Trigger the epic creation by running /create-epics for the applicable layer or system to generate epics from approved GDDs and architecture.

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 from architecture decisions for project management?▼

You create epics from approved architecture decisions by generating one epic per architectural module, ensuring each piece of work references governing ADRs, engine risk, and untraced requirements for proper governance.

What is the best way to map software delivery work to architectural modules?▼

Mapping software delivery work to architectural modules involves processing epics in dependency-safe order across Foundation, Core, Feature, and Presentation layers to generate discrete, governed work items.

How do I link ADR governance and untraced requirements to project epics?▼

Linking ADR governance to epics requires referencing ADR coverage and TR requirements during generation, which surfaces untraced items for ADR planning directly within each module's epic scope.

Do I need approved GDDs before generating epics across system layers?▼

Yes, you need approved GDDs and established architecture before generating epics, because the process translates those approved design documents into tracked work mapped to Foundation, Core, Feature, and Presentation layers.

Can I review generated epics before they are written to files?▼

Yes, the epic generation process requires user approval before writing any files, ensuring you can review the proposed epics, ADR references, and risk mappings for each architectural module.

Why does epic generation follow a layered workflow across Foundation and Core layers?▼

Epic generation follows a layered workflow across Foundation, Core, Feature, and Presentation layers to process work in dependency-safe order, ensuring foundational architectural modules are addressed before higher-level features.

Related Skills

Explore More Software Engineering Skills→
Eigo-Mt-FujiEigo-Mt-Fuji

traceability-auditor

Analyze project artifacts to generate traceability matrices and coverage metrics.

Community
Advanced
rakhnianskii9rakhnianskii9

create-epics

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

Community
Advanced
adolfoaranaes12adolfoaranaes12
2

adr-examples

Translate PRDs and Epics into architecture documents with ADRs.

Community
Basic
HechaoYannetHechaoYannet

create-epics

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

Community
Advanced