Create Epics

---
name: create-epics
description: >-
  Optionally group a large approved GDD/architecture outcome into an epic that owns several independently closable task contracts. Use for multi-task roadmap planning, not routine bugs or bounded features. In the canonical task-first workflow create tasks directly after the epic; do not add a separate story layer.
---

# Create Epics

Codex port of Claude Code Game Studios /create-epics.

Use this skill when the task matches the workflow described below. Keep the
Codex version lightweight: load `references/claude-skill.md` only when the
original detailed Claude workflow is needed.

## Codex Workflow

1. Read repository-local instructions first: `AGENTS.md`, `CLAUDE.md`, the
   nearest path-scoped instructions (`Assets/CLAUDE.md` for Unity when present),
   and any referenced project docs.
2. Use this workflow's intent, but follow Codex tool and collaboration rules.
3. Apply SOLID, Clean Code, clear English naming, dependency boundaries, and
   focused tests for new or changed expected behavior.
4. When a Claude workflow mentions a custom agent, treat it as a role reference.
   Do the work locally unless the user explicitly asks for sub-agents or
   parallel agent work.
5. For implementation tasks, make the change directly when the request is clear;
   ask only when a decision cannot be safely inferred from local context.
6. Verify with the repository's available checks and summarize changed files,
   tests run, and residual risk.

## Original Workflow Summary

Translate approved GDDs and architecture into optional grouping epics. An epic
is never implemented directly and does not require child story files. Create
one `create-task` contract per independently verifiable deliverable.

## Detailed Reference

- Original Claude skill: `references/claude-skill.md`