LogoSkills

project:epic

Stage 5: Epic Creation — ZenHub Epic/Story creation, sprint planning

항ëĒŠë‚´ėšŠ
Invoke/project:epic
Categorypipeline
Complexitymoderate
MCP Serverszenhub

/project:epic#

Stage 5: Epic Creation — Creates ZenHub Epics and Stories based on design artifacts.

Triggers#

  • When creating development issues after Design stage completion
  • When splitting architecture/UX specs into actionable work units

Usage#

/project:epic
/project:epic --sprint current
/project:epic --feature community --entity Post

Options#

OptionDefaultDescription
--sprint None Sprint assignment (current, next, number)
--featureslugFeature name (snake_case)
--entityAuto-inferredEntity name (PascalCase)

Prerequisites#

  • Design stage completed (Solutioning Gate passed)
  • Architecture Doc, UX Spec artifacts exist

Execution Flow#

Phase 1: Epic Creation#

Source: cc-dev-cycle

  1. ZenHub Epic creation (/zenhub:epic)
    • Structure Epic based on Architecture Doc
    • Feature/Entity mapping
    • Link design artifacts in Epic description

Phase 2: Story Writing#

Source: cc-bmad

  1. Individual Story writing (/bmad:create-story)

    • Screen-based Stories from UX Spec
    • Technical Stories from Architecture
    • Connect BDD scenarios as Acceptance Criteria
    • Set dependency relationships

  2. Sprint planning (/bmad:sprint-planning)

    • Story priority determination
    • Sprint assignment
    • Capacity planning

Phase 3: PM Review#

Source: cc-bmad (PM persona)

  1. Story quality verification
    • Story point estimation
    • Labeling (type, scope, priority)
    • Dependency verification
    • Acceptance Criteria completeness check

Phase 4: Planning Gate#

BMAD Planning Gate verification:

  • Epic/Story structure (epic_story_structure)
  • Story points (story_point)
  • Labeling (labeling)
  • Dependencies (dependencies)

Artifacts#

  • ZenHub Epic (issue number recorded)
  • Linked Stories (issue number list)
  • Epic number recorded in .pipeline/{slug}.yaml

After Completion#

  • Verify Planning Gate passed
  • Record Epic/Story numbers in state file
  • Present context-clear handoff:
✅ Epic Creation stage complete (Planning Gate PASSED).
  Epic #{epic_number} created with {story_count} Stories.

**Option 1 (Recommended)**: Clear context and continue to Development
  /clear
  Then run: /project:develop --epic {epic_number}

**Option 2**: Continue in current context
  Proceed directly to /project:develop --epic {epic_number}