@cloudkinetix/bmad-enhanced/expansion-packs/ck-parallel-dev/workflows/parallel-story-execution.yaml

Cloud-Kinetix enhanced fork of BMAD-METHOD - Breakthrough Method of Agile AI-driven Development with robust versioning and unified validation.

name: parallel-story-execution
title: Parallel Story Execution Workflow
description: Execute multiple user stories in parallel with intelligent conflict detection and wave management
type: execution
category: parallel-development
estimated_time: 1-2 sprints

agents:
  - sm
  - dev
  - architect
  - qa

prerequisites:
  - Stories refined and ready
  - Acceptance criteria clear
  - Team capacity available
  - Git worktree support

startup_sequence:
  - agent: sm
    task: parallel-planning-session
    message: "Planning parallel story execution with conflict analysis"

story_analysis_phase:
  - id: 1.1
    agent: sm
    task: story-dependency-mapping
    outputs:
      - Story dependency graph
      - Parallel execution groups
      - Critical path identification
      - Resource requirements

  - id: 1.2
    agent: architect
    task: technical-conflict-analysis
    inputs:
      - Story specifications
      - System architecture
    outputs:
      - File conflict matrix
      - Component dependencies
      - Risk heat map
      - Mitigation strategies

  - id: 1.3
    agent: dev
    task: wave-assignment
    inputs:
      - Conflict analysis
      - Team capacity
    outputs:
      - Wave assignments
      - Developer allocation
      - Worktree plan
      - Timeline estimate

execution_setup_phase:
  - id: 2.1
    agent: dev
    task: parallel-environment-setup
    outputs:
      - Worktrees created
      - Branch naming applied
      - CI/CD configured
      - Development tools ready

  - id: 2.2
    agent: sm
    task: kickoff-coordination
    outputs:
      - Team briefing complete
      - Communication plan
      - Progress tracking setup
      - Success criteria shared

wave_execution_phase:
  - id: 3.1
    agent: dev
    task: wave-1-implementation
    parallel: true
    workers: "based on team size"
    outputs:
      - Story implementations
      - Unit test coverage
      - Code reviews completed
      - Documentation updated

  - id: 3.2
    agent: qa
    task: parallel-story-testing
    parallel: true
    continuous: true
    outputs:
      - Story test results
      - Defect reports
      - Test automation
      - Quality metrics

  - id: 3.3
    agent: dev
    task: cross-wave-coordination
    continuous: true
    outputs:
      - Sync status maintained
      - Conflicts detected early
      - Dependencies managed
      - Progress visualized
    decision_points:
      - id: D1
        name: Wave Transition
        description: Decide when to proceed to next wave

integration_phase:
  - id: 4.1
    agent: dev
    task: story-integration
    sequential: true
    outputs:
      - Stories merged
      - Conflicts resolved
      - Integration tested
      - Build validated

  - id: 4.2
    agent: qa
    task: integration-validation
    outputs:
      - End-to-end tests
      - Cross-story validation
      - Performance impact
      - Regression results

  - id: 4.3
    agent: sm
    task: acceptance-coordination
    outputs:
      - Demo preparation
      - Stakeholder review
      - Acceptance sign-off
      - Feedback captured

optimization_phase:
  - id: 5.1
    agent: architect
    task: parallel-efficiency-review
    outputs:
      - Efficiency metrics
      - Bottleneck analysis
      - Improvement suggestions
      - Pattern identification

  - id: 5.2
    agent: sm
    task: process-refinement
    outputs:
      - Updated wave strategies
      - Team feedback incorporated
      - Process documentation
      - Best practices captured

decision_points:
  - id: D1
    step: 3.3
    description: Wave transition timing
    options:
      - All stories in wave complete
      - 80% completion threshold
      - Time-boxed waves
      - Dynamic progression
    impacts:
      - Integration complexity
      - Team utilization
      - Feedback timing
      - Risk exposure

  - id: D2
    step: 4.1
    description: Integration approach
    options:
      - Sequential by priority
      - Parallel integration branches
      - Feature toggle isolation
      - Continuous integration
    impacts:
      - Merge complexity
      - Testing effort
      - Rollback options
      - Time to done

parallel_execution_patterns:
  conflict_strategies:
    - File-level isolation
    - Component boundaries
    - API contracts
    - Database migrations

  coordination_tools:
    - Real-time dashboards
    - Automated conflict alerts
    - Progress visualization
    - Dependency tracking

  quality_assurance:
    - Parallel test execution
    - Isolated test environments
    - Continuous integration
    - Automated validation

success_metrics:
  - Stories completed per sprint
  - Parallel efficiency ratio
  - Integration success rate
  - Quality metrics maintained
  - Team velocity improvement
  - Cycle time reduction

anti_patterns_to_avoid:
  - Over-parallelization causing conflicts
  - Insufficient coordination
  - Delayed integration
  - Resource contention
  - Communication silos

outputs:
  - Completed story implementations
  - Integrated and tested code
  - Updated documentation
  - Process metrics
  - Lessons learned
  - Improved practices