@cloudkinetix/bmad-enhanced/expansion-packs/ck-parallel-dev/workflows/parallel-bug-fixing.yaml

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

name: parallel-bug-fixing
title: Parallel Bug Fixing Workflow
description: Efficiently fix multiple bugs in parallel with isolation and comprehensive testing
type: maintenance
category: parallel-development
estimated_time: varies by bug count and severity

agents:
  - dev
  - qa
  - architect
  - sm

prerequisites:
  - Bug list prioritized
  - Reproduction steps documented
  - Test environments available
  - Git worktree support

startup_sequence:
  - agent: qa
    task: bug-triage-session
    message: "Analyzing bugs for parallel fixing potential"

analysis_phase:
  - id: 1.1
    agent: qa
    task: bug-categorization
    outputs:
      - Bug severity matrix
      - Component mapping
      - Reproduction complexity
      - Test requirements
    decision_points:
      - id: D1
        name: Parallelization Approach
        description: Determine bug fixing strategy

  - id: 1.2
    agent: architect
    task: impact-analysis
    inputs:
      - Bug list
      - System architecture
    outputs:
      - Code impact analysis
      - Risk assessment
      - Conflict potential
      - Fix complexity

  - id: 1.3
    agent: dev
    task: parallel-feasibility
    outputs:
      - Parallelizable bug groups
      - Sequential requirements
      - Resource allocation
      - Timeline estimates

setup_phase:
  - id: 2.1
    agent: dev
    task: bug-fix-environment-setup
    outputs:
      - Worktrees per bug/group
      - Isolated environments
      - Debug tools configured
      - Test data prepared

  - id: 2.2
    agent: qa
    task: test-harness-preparation
    outputs:
      - Regression test suite
      - Bug-specific tests
      - Automated validators
      - Performance baselines

parallel_fixing_phase:
  - id: 3.1
    agent: dev
    task: bug-reproduction
    parallel: true
    outputs:
      - Reproduction confirmed
      - Root cause identified
      - Debug information
      - Fix approach defined

  - id: 3.2
    agent: dev
    task: implement-fixes
    parallel: true
    outputs:
      - Bug fixes implemented
      - Unit tests added
      - Code reviewed
      - Documentation updated
    decision_points:
      - id: D2
        name: Fix Validation
        description: Determine validation approach

  - id: 3.3
    agent: qa
    task: parallel-fix-testing
    parallel: true
    continuous: true
    outputs:
      - Fix verification
      - Side effect testing
      - Regression results
      - Performance impact

integration_phase:
  - id: 4.1
    agent: dev
    task: fix-integration
    sequential: "by priority"
    outputs:
      - Fixes merged safely
      - Conflicts resolved
      - Build validation
      - Integration tested

  - id: 4.2
    agent: qa
    task: comprehensive-regression
    outputs:
      - Full regression suite
      - Cross-fix validation
      - System stability
      - Performance verified

  - id: 4.3
    agent: architect
    task: fix-review
    outputs:
      - Code quality review
      - Architecture impact
      - Technical debt
      - Future prevention

release_preparation:
  - id: 5.1
    agent: sm
    task: fix-communication
    outputs:
      - Release notes drafted
      - Customer communication
      - Deployment plan
      - Rollback strategy

  - id: 5.2
    agent: qa
    task: release-validation
    outputs:
      - Release candidate tested
      - Deployment verified
      - Monitoring configured
      - Success criteria met

decision_points:
  - id: D1
    step: 1.1
    description: Choose parallelization strategy
    options:
      - Component-based groups
      - Severity-based waves
      - Developer expertise groups
      - Risk-based sequencing
    impacts:
      - Fix delivery speed
      - Integration complexity
      - Resource efficiency
      - Quality assurance

  - id: D2
    step: 3.2
    description: Fix validation approach
    options:
      - Immediate testing per fix
      - Batch testing by wave
      - Continuous integration
      - Risk-based validation
    impacts:
      - Feedback speed
      - Resource usage
      - Quality confidence
      - Release timing

bug_fixing_patterns:
  isolation_strategies:
    - Worktree per bug
    - Component isolation
    - Feature flag protection
    - Database snapshots

  coordination_methods:
    - Daily bug triage
    - Fix progress tracking
    - Conflict monitoring
    - Knowledge sharing

  quality_gates:
    - Reproduction validation
    - Fix verification
    - Regression testing
    - Performance validation

success_criteria:
  - All critical bugs fixed
  - No regression introduced
  - Fix time reduced by parallel execution
  - Code quality maintained
  - Customer satisfaction improved

monitoring:
  - Bugs fixed per day
  - Parallel efficiency
  - Regression rate
  - Integration success
  - Time to resolution

outputs:
  - Fixed and tested code
  - Comprehensive test suite
  - Release documentation
  - Process metrics
  - Prevention recommendations
  - Knowledge base updates