Triggers#

• When creating development issues after Design stage completion
• When splitting architecture/UX specs into actionable work units
• When the pipeline covers multiple features → create a Project-level issue wrapping the Epics

Usage#

/product:epic
/product:epic --sprint current
/product:epic --feature community --entity Post
/product:epic --project-level                       # Project 이슈 생성 후 Epic들을 하위로 연결
/product:epic --parent-project 1024                  # 기존 Project 이슈에 Epic 연결

Options#

Initiative/Project issue type availability is checked dynamically via getIssueTypes() — if the workspace has no Initiative/Project type, falls back to the next level down (Project, then Epic) top-level, with a warning.

Prerequisites#

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

Execution Flow#

Phase 0: Hierarchy & Priority Review (before creation)#

Source: cc-dev-cycle

0. Hierarchy decision + priority scoring
   • With --project-level: derive Project title/scope from .pipeline/{slug}.yaml
   • Score every Epic/Story to be created: dependency (blocker) / business value / risk / effort
   • Assign tiers p0/p1/p2 — labels are immutable after creation, so this must precede Phase 1
   • Present the priority table to the user for confirmation

Phase 1: Initiative/Project/Epic Creation#

Source: cc-dev-cycle

0. ZenHub Initiative creation (with --initiative-level, /zenhub:epic --initiative)
   • One Initiative issue wrapping the Project (or Epics directly, if no --project-level)
1. ZenHub Project creation (with --project-level, /zenhub:epic --project)
   • One Project issue wrapping all feature Epics
   • Goals, Epic list, and priority table in the Project description
   • Linked to the Initiative via parentIssueId when --initiative-level/--parent-initiative is used
2. ZenHub Epic creation (/zenhub:epic)
   • Structure Epic based on Architecture Doc
   • Feature/Entity mapping
   • Link design artifacts in Epic description
   • Linked to the Project via parentIssueId when applicable

Phase 2: Story Writing#

Source: cc-product

3. Individual Story writing (/product:create-story)

   • Screen-based Stories from UX Spec
   • Technical Stories from Architecture
   • Connect BDD scenarios as Acceptance Criteria
   • Set dependency relationships
   • Apply Phase 0 priority labels at creation

4. Sprint planning (/product:sprint-planning)

   • Story priority determination
   • Sprint assignment
   • Capacity planning

Phase 3: PM Review#

Source: cc-product (PM persona)

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

Phase 3.5: Pipeline Sorting (skipped with --no-sort)#

Source: cc-dev-cycle (rules/zenhub-conventions.md → Priority Review and Pipeline Sorting)

6. Priority-based pipeline placement
   • Project/Epic → Product Backlog
   • Story P0 → Sprint Backlog (+ sprint assignment when --sprint)
   • Story P0/P1 (no sprint) → Product Backlog, P2 → Icebox
   • Move in descending priority order (P0 → P1 → P2) — moveIssueToPipeline has no position param, so ordering is approximated by move sequence and recorded as a priority table in the Epic/Project body

Phase 4: Planning Gate#

BMAD Planning Gate verification:

• Project/Epic/Story hierarchy (epic_story_structure)
• Story points (story_point)
• Labeling incl. priority tiers (labeling)
• Dependencies (dependencies)
• Pipeline placement matches priority matrix (pipeline_sorting)

Artifacts#

• ZenHub Project (issue number recorded, with --project-level)
• ZenHub Epic (issue number recorded)
• Linked Stories (issue number list)
• Priority table (.claude/docs/{feature}/zenhub/priority.md)
• Project/Epic numbers recorded in .pipeline/{slug}.yaml

After Completion#

• Verify Planning Gate passed
• Record Project/Epic/Story numbers in state file
• Present context-clear handoff:

✅ Epic Creation stage complete (Planning Gate PASSED).
  Project #{project_number} (optional) / Epic #{epic_number} created with {story_count} Stories.
  Pipeline sorting: P0 ×{n} → Sprint Backlog, P1 ×{n} → Product Backlog, P2 ×{n} → Icebox

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

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