What is create-epics?

A planning tool that turns approved product requirements and architecture into epics, which are large groups of related development work. Each epic records its scope, technical decisions, risks, and uncovered requirements.

Use it after architecture review to organize work by system or module before breaking each epic into stories.

It connects high-level architecture to the work that developers will later implement as individual stories.

create-epics — Skill for Claude Code by cenconq25

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add cenconq25/claude-code-app-studio --skill create-epics

Clone the repo

git clone --depth 1 https://github.com/cenconq25/claude-code-app-studio

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/create-epics/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/create-epics)

Your own site

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/create-epics"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/create-epics/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/create-epics"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/create-epics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,903 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00066	$0.01903
Opus 5.5	$0.00026	$0.00761
Sonnet 5.5	$0.00013	$0.00381
Haiku 4.5	$0.00007	$0.00190

Measured 1mo ago against content hash 8c6e18cf1279, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-epics scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/create-epics/SKILL.md · 229 lines

How it starts

The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Epics

An epic is the unit between architecture and stories. It groups related stories under a shared system or module, declares the governing ADRs, and surfaces the framework risk so the engineer knows what to verify before coding.

Output: production/epics/<epic-slug>/EPIC.md (one file per epic)

Purpose / When to Run

Run when:

/architecture-review returned PASS or CONCERNS (not FAIL)
/create-control-manifest is written and dated
The team is ready to plan stories

Do not decompose into stories here — /create-stories <epic-slug> does that.

Inputs

All design/prd/*.md
All Accepted docs/architecture/ADR-*.md
docs/architecture/architecture.md
docs/architecture/control-manifest.md
docs/framework-reference/<framework>/
Optional <system-name> argument: only generate the epic for this system

Outputs

production/epics/<epic-slug>/EPIC.md — one per system in scope

Phase 1: Pre-checks

Confirm at least one Accepted ADR exists
Confirm docs/architecture/control-manifest.md exists and read its Manifest Version
If a previous epic for the same system exists, ask: Refresh, Replace, Cancel

If <system-name> argument given, scope to that system; else, do all in-scope MVP systems from the systems index.

Phase 2: Read All Context

Read the inputs in full. Hold:

Each PRD's Detailed Requirements (all TR-IDs)
Each PRD's Acceptance Criteria
Each ADR's PRD Requirements Addressed table
Architecture Section 3 (Layers) and Section 20 (Required ADRs)
Control manifest Required/Forbidden/Guardrail by layer

Phase 3: Group TR-IDs into Epics

The mapping rule: one epic per system, with stories living inside.

Special cases:

If a system is huge (>30 TR-IDs), split into 2-3 sub-epics (e.g., "Auth — Sign-in", "Auth — Account & Recovery")
Foundation systems (state, navigation, networking) become epics if they need any user-visible scaffolding work
Cross-cutting concerns (analytics, error reporting) become their own epics if they have ≥3 TR-IDs of dedicated work

Read the full file on GitHub · 229 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 229 lines · 66 tokens per session scan A 8c6e18cf1279

Subscribe to this mod's changes

create-epics is a skill published in the GitHub repository cenconq25/claude-code-app-studio (42 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 1,903 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Planning Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens