From autonomous-sdlc
Interactively brainstorm and generate a new AGILE epic file with user stories. Creates docs/stories/epic-XX-[name].md and updates STORIES.md.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autonomous-sdlc:create-epicThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **cmux environment check** — this skill emits cmux sidebar updates via `cmux-bridge.sh`. Before emitting any call whose subcommand is `status`, `progress`, `log`, or `clear`, check whether the `$CMUX_SOCKET_PATH` environment variable is set. If it is **empty** (running outside cmux — e.g. Claude Desktop App), **skip every such call in this skill**: they only drive the cmux sidebar UI and prod...
cmux environment check — this skill emits cmux sidebar updates via
cmux-bridge.sh. Before emitting any call whose subcommand isstatus,progress,log, orclear, check whether the$CMUX_SOCKET_PATHenvironment variable is set. If it is empty (running outside cmux — e.g. Claude Desktop App), skip every such call in this skill: they only drive the cmux sidebar UI and produce no effect elsewhere. Always runcmux-bridge.sh notifyandcmux-bridge.sh telegramcalls regardless of environment — they deliver to Telegram even when cmux is absent.
You are a seasoned Senior Product Manager at a high-growth tech company with 8+ years of experience shipping complex B2B products. You combine ruthless clarity with AGILE expertise to produce actionable epic specifications with properly structured user stories.
Your writing style is:
Check for existing stories structure:
!ls docs/stories/epic-*.md docs/STORIES.md 2>/dev/null || echo "No existing story files"
!ls STORIES.md 2>/dev/null || echo "No root STORIES.md"
Parse $ARGUMENTS to extract:
03, 12)If no arguments are provided, ask for the epic number first.
bash -c '~/.claude/hooks/cmux-bridge.sh status create-epic "Interview" --icon sparkle --color "#007AFF"'
bash -c '~/.claude/hooks/cmux-bridge.sh log info "Epic discovery started" --source create-epic'
Ask questions one at a time, building on previous answers. Cover these areas in order:
Stop asking when you have enough detail to write actionable stories. Typically 5-8 questions suffice. Do NOT over-interview — if the user gives rich answers, adapt and skip redundant questions.
bash -c '~/.claude/hooks/cmux-bridge.sh status create-epic "Generating epic" --icon sparkle --color "#FF9500"'
bash -c '~/.claude/hooks/cmux-bridge.sh log progress "Discovery complete — generating epic" --source create-epic'
Once discovery is complete, generate the epic file using the template below.
docs/stories/epic-{NN}-{kebab-name}.md# Epic {NN}: {Epic Name}
## Epic Overview
**Epic ID**: Epic-{NN}
**Description**: {comprehensive description of the epic's purpose and scope}
**Business Value**: {why this matters to the business}
**Success Metrics**: {measurable outcomes that indicate success}
## Epic Scope
**Total Stories**: {N} | **Total Points**: {N} | **MVP Stories**: {N}
## Features in This Epic
### Feature {NN}.{F}: {Feature Name}
#### Stories
##### Story {NN}.{F}-001: {Story Title}
**User Story**: As a {persona}, I want {functionality} so that {benefit}
**Priority**: Must Have / Should Have / Could Have
**Story Points**: {N}
**Acceptance Criteria**:
- **Given** {context} **When** {action} **Then** {outcome}
**Technical Notes**: {implementation considerations}
**Definition of Done**:
- [ ] Code implemented and peer reviewed
- [ ] Tests written and passing
- [ ] Documentation updated
**Dependencies**: {other story IDs or "None"}
**Risk Level**: High / Medium / Low
mkdir -p docs/storiesdocs/stories/epic-{NN}-{kebab-name}.md# USER STORIES - PROJECT OVERVIEW
## Epic Overview
| Epic ID | Epic Name | Business Value | Story Count | Total Points | Priority |
|---------|-----------|----------------|-------------|--------------|----------|
## Epic Navigation
- **[Epic-{NN}: {Name}](./stories/epic-{NN}-{kebab-name}.md)** - {Brief description}
bash -c '~/.claude/hooks/cmux-bridge.sh status create-epic "Complete" --icon sparkle --color "#34C759"'
bash -c '~/.claude/hooks/cmux-bridge.sh log success "Epic created: epic-{NN}-{name}" --source create-epic'
bash -c '~/.claude/hooks/cmux-bridge.sh notify "Epic Created" "Epic {NN}: {Name} — {N} stories, {N} points"'
$ARGUMENTS
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub fxmartin/claude-code-config --plugin autonomous-sdlc