create-epics

Translate approved GDDs and architecture into bounded epics per module.

Updated Apr 10, 2026

Search Tags:#architecture #production #adr #governance #epic #project-management #gdd

Ready to run

npx skills add https://github.com/emcconnell/nova-scout --skill create-epics-emcconnell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-epics
Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/create-epics
Command: npx skills add https://github.com/emcconnell/nova-scout --skill create-epics-emcconnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate approved GDDs and architecture into bounded epics for each module, ensuring clear ownership and traceability to ADRs and engine risk assessments.

Core Features & Use Cases

Maps each architectural module to a bounded epic and captures scope, governing ADRs, and engine risk.
Flags untraced requirements and prompts for ADR creation before proceeding.
Updates the production epic index and writes EPIC.md files once approved.

Quick Start

Run /create-epics all to generate epics for every system in layer order.

Frequently Asked Questions about create-epics

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

FAQPage Schema

How do I translate approved architecture documents into trackable project epics?▼

To translate architecture into trackable epics, this Skill maps each architectural module to a bounded epic, capturing scope, governing ADRs, and engine risk assessments. It processes approved GDDs in layer order and writes EPIC.md files.

How do I generate epics for every system in layer order from a GDD?▼

You can generate epics for every system in layer order by running the generation command for all modules. This applies layer-based processing to your approved GDDs and creates bounded epics for each architectural component.

What happens to untraced requirements when creating epics from architecture?▼

When creating epics from architecture, untraced requirements are flagged automatically. The system surfaces these governance gaps and prompts for ADR creation before proceeding to ensure full traceability.

Does this epic generation process link modules to ADRs and engine risk assessments?▼

Yes, this epic generation process links each module to its governing ADRs and engine risk assessments. It surfaces governance data during translation to ensure clear ownership and traceability across the architecture.

When do I need to update the production epic index after architecture translation?▼

You need to update the production epic index after architecture translation once the generated epics are approved. The system automatically updates this index and writes the corresponding EPIC.md files to the production directory.

Best way to ensure clear ownership and traceability when breaking down architecture into epics?▼

The best way to ensure clear ownership and traceability when breaking down architecture into epics is to map each module to a bounded epic with explicit ADR governance. Flagging untraced requirements before approval ensures no architectural decisions are missed.