/project:develop#

Stage 6: Development — Iterates through Stories within an Epic, executing the cc-dev-cycle 13-step development cycle.

Triggers#

• When starting development after Epic Creation completion
• When implementation of a specific Epic or Issue is needed

Usage#

# Full Epic development
/project:develop --epic 42

# Single issue development
/project:develop --issue 1810

# Auto from pipeline context
/project:develop

# Parallel development of independent Stories (Agent Teams)
/project:develop --epic 42 --parallel

Parameters#

*Either epic or issue is required. In pipeline context, epic number is automatically referenced.

Options#

Prerequisites#

• Epic Creation stage completed (Planning Gate passed)
• ZenHub Epic and Stories exist
• For --parallel: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 environment variable required

Execution Flow#

Epic Mode (--epic)#

0. Agent Teams Prerequisite Check (for --parallel)

if --parallel:
  Check helpers.md#Check-Agent-Teams-Available
  if teams_available = false:
    ⚠ Agent Teams not available. Falling back to sequential mode.
    → Auto-switch to sequential processing

1. Story List Retrieval

• Fetch Story list within Epic from ZenHub
• Sort by dependency order
• Check status (skip already completed Stories)

2-A. Sequential Execution (default)

For each Story:

a. Story implementation preparation (cc-bmad: /bmad:dev-story)

• Story detailed analysis
• Implementation plan creation
• Required files/components identification

b. 13-step development cycle (cc-dev-cycle: /dev:run {issue_number})

• Steps 1-12 sequential execution

c. Implementation review (cc-bmad: Flutter/Backend Dev persona)

• Implementation quality verification
• Architecture compliance check

2-B. Parallel Execution (--parallel, when Agent Teams active)

Phase 1: Dependency Analysis + File Ownership Boundary Analysis

1. Build Story dependency graph
   - Check each Story ' s dependencies field
   - Identify blocking relationships

2. File ownership boundary analysis
   - Map Story → source directory from architecture docs
   - Detect overlapping file areas
   - If overlap found → move those Stories to sequential queue

3. Identify independent Story groups (max 3 teams)
   ┌─ Group A: [STORY-001, STORY-003] — independent file areas
   ├─ Group B: [STORY-002]            — independent file areas
   └─ Sequential Queue: [STORY-004]   — depends on STORY-001

Phase 2: User Approval (plan confirmation)

╔════════════════════════════════════════════════════════════════╗
║  Parallel Development Plan                                     ║
╠════════════════════════════════════════════════════════════════╣
║                                                                ║
║  Parallel Teams (Agent Teams):                                 ║
║    Team 1: STORY-001, STORY-003                                ║
║      └─ Files: lib/src/feature/author/                         ║
║    Team 2: STORY-002                                           ║
║      └─ Files: lib/src/feature/book/                           ║
║                                                                ║
║  Sequential Queue (dependencies):                              ║
║    STORY-004 (depends on STORY-001)                            ║
║                                                                ║
║  Estimated teammates: 2                                        ║
║                                                                ║
╚════════════════════════════════════════════════════════════════╝

Proceed with this plan? (y/n)

Phase 3: Delegate to /bmad:team-dev

Independent Story groups → delegate to /bmad:team-dev
  - helpers.md#Spawn-BMAD-Teammate (developer role)
  - helpers.md#Create-Team-Task-List
  - Pass file ownership boundaries to each teammate
  - Separate branches per teammate

After completion, Lead performs integration verification:
  - helpers.md#Collect-Team-Results
  - helpers.md#Team-Quality-Gate

Phase 4: Sequential Queue Processing

Stories with dependencies execute sequentially after parallel work completes:
  for story in sequential_queue:
    /dev:run {story.issue_number}

3. Progress Tracking

• Update .pipeline/{slug}.yaml on each Story completion
• Record failed Stories

Single Issue Mode (--issue)#

• Directly execute cc-dev-cycle 13 steps
• Update pipeline state

Implementation Gate#

BMAD Implementation Gate verification (per Story):

• Lint passed (dart analyze, dcm analyze)
• Tests passed
• Code review passed
• Branch naming convention followed

Artifacts#

• Implementation code (per Story: branch → PR → merge)
• Completed Story list in .pipeline/{slug}.yaml

After Completion#

• Verify all Stories completed
• Verify Implementation Gate passed
• Update .pipeline/{slug}.yaml state
• Present context-clear handoff:

✅ Development stage complete (all Implementation Gates PASSED).
  {completed_count}/{total_count} Stories merged.

**Option 1 (Recommended)**: Clear context and continue to Launch
  /clear
  Then run: /project:launch

**Option 2**: Continue in current context
  Proceed directly to /project:launch