Command
/plan-epics
briefs → GitHub epics + user stories
Turn a brief into GitHub epics and linked, labelled stories.
See it run
/plan-epics runs, in order.How to run it
Run it in your harness
/plan-epics <brief text | path to a brief file | several briefs> [area/label hints] [dry-run] [optional role hints — e.g. "also involve architect and UX"]<angle brackets> = required · [square brackets] = optional
How it works
Product-manager always authors the backlog. Up to two more specialists join when the brief implicates their domain — or when you name them. A bookkeeping brief stays PM-only.
Read
Take the brief, the repo's labels, and what is already open, then pick the panel.
No specialist yet — intake and panel selection are the run.
Slice
Split the work into epics with clear edges. The panel is product-manager plus at most two of the roles below.
Always
Also sit when
architectnew subsystems, schema, or platform boundariesux-ui-designerscreens, flows, design system, accessibilityart-directorrendered art in an art-producing domaindata-scientistdata, ML, metrics, or experimentationperformance-engineerlatency, throughput, or resource limitsdevops-engineerbuild, CI, packaging, or toolchain pinssecurity-engineerauth, secrets, crypto, or untrusted inputsite-reliability-engineerreliability, incidents, rollback, or SLOstechnical-writerdocumented behaviour or public API/CLI
Write
One product-manager per epic authors the stories. The same panel then reviews slices in their domain.
Always
Also sit when
architectnew subsystems, schema, or platform boundariesux-ui-designerscreens, flows, design system, accessibilityart-directorrendered art in an art-producing domaindata-scientistdata, ML, metrics, or experimentationperformance-engineerlatency, throughput, or resource limitsdevops-engineerbuild, CI, packaging, or toolchain pinssecurity-engineerauth, secrets, crypto, or untrusted inputsite-reliability-engineerreliability, incidents, rollback, or SLOstechnical-writerdocumented behaviour or public API/CLI
Create
Open the issues on GitHub, attach each story as a sub-issue of its epic, and verify they connect.
No extra spawn — the run creates what the panel wrote.
When to use
- You know the work, but GitHub has no epics or stories yet.
- Ready to build? /ship-epic. Messy existing backlog? /consolidate-issues.
The skill
The installer ships the full skill — stages, gates, config — from commands/plan-epics.md.