workflow: id: parallel-story-development name: Parallel Story Development with BMAD Integration description: Orchestrates multiple dev agents working simultaneously on different stories using git worktrees, with progressive sophistication and DoD enforcement type: development project_types: - multi-story-sprint - parallel-feature-development - rapid-iteration phases: preparation: description: Story validation and dependency analysis duration: 30-60 minutes wave-execution: description: Parallel story implementation in waves duration: varies by story count integration: description: Merge and quality validation duration: 1-2 hours full_sequence: - agent: sm action: validate-story-readiness validates: 3-tier-validation-system creates: story-validation-report.md description: Comprehensive validation using critical/warning/suggestion tiers notes: | - Critical issues block execution - Warnings require justification to override - Suggestions are informational only - All overrides are logged for process improvement - agent: parallel action: analyze-and-plan requires: story-validation-report.md creates: - dependency-analysis.md - .bmad-workspace/ck-parallel-dev/runs/{{run-id}}/pre-execution-report.md - .bmad-workspace/ck-parallel-dev/runs/{{run-id}}/execution-plan.json - .bmad-workspace/ck-parallel-dev/runs/{{run-id}}/rollback-guide.md description: Perform deep semantic analysis and generate comprehensive execution plan with git worktree commands notes: | - Combines semantic dependency analysis with practical execution planning - Includes specific git worktree commands and BMAD prompts - Creates audit trail for potential rollback - Provides Go/No-Go recommendation - Requires user approval before proceeding user_approval_required: true critical: true - agent: parallel action: setup-worktrees requires: - .bmad-workspace/ck-parallel-dev/runs/{{run-id}}/execution-plan.json creates: worktree-manifest.md description: Create git worktrees for each story based on the execution plan notes: Each story gets isolated environment with specific branch naming - agent: parallel action: execute-concurrent-wave-1 execution_mode: maximum_parallelism coordination_strategy: concurrent_multi_tool_execution parallel_strategy: approach: simultaneous_task_calls execution: "4 concurrent Task tool calls in single message" requires: worktree-manifest.md validates: story-dod-checklist creates: concurrent-wave-1-completion.md description: Execute first wave using concurrent Task deployment with unique innovation dimensions sophistication: 1 concurrent_agents: AGENT_A: innovation_dimension: error_handling conflict_zones: [authentication_flow] AGENT_B: innovation_dimension: testing_strategies conflict_zones: [test_environment] AGENT_C: innovation_dimension: security_hardening conflict_zones: [ai_prompts] AGENT_D: innovation_dimension: monitoring_approach conflict_zones: [session_handling] notes: True parallelism through concurrent Task tool calls in single message - agent: qa action: quality-gate-1 requires: wave-1-completion.md validates: quality-metrics creates: quality-report-wave-1.md description: Run tests, linting, and coverage checks for wave 1 blocking: true - agent: parallel action: execute-concurrent-wave-2 execution_mode: maximum_parallelism coordination_strategy: concurrent_multi_tool_execution requires: quality-report-wave-1.md validates: story-dod-checklist creates: concurrent-wave-2-completion.md description: Execute second wave with concurrent enhanced features sophistication: 2 concurrent_agents: AGENT_E: innovation_dimension: performance_optimization conflict_zones: [database_queries] AGENT_F: innovation_dimension: user_experience conflict_zones: [ui_components] AGENT_G: innovation_dimension: api_design conflict_zones: [service_layer] AGENT_H: innovation_dimension: code_organization conflict_zones: [shared_utilities] notes: Concurrent execution builds on wave 1 with enhanced sophistication - agent: qa action: quality-gate-2 requires: wave-2-completion.md validates: quality-metrics creates: quality-report-wave-2.md description: Comprehensive testing of enhanced features - agent: parallel action: execute-concurrent-wave-3 execution_mode: maximum_parallelism coordination_strategy: concurrent_multi_tool_execution requires: quality-report-wave-2.md optional: true validates: story-dod-checklist creates: concurrent-wave-3-completion.md description: Execute third wave with concurrent advanced optimizations sophistication: 3 concurrent_agents: AGENT_I: innovation_dimension: scalability_patterns conflict_zones: [infrastructure] AGENT_J: innovation_dimension: documentation_quality conflict_zones: [api_docs] AGENT_K: innovation_dimension: efficiency_patterns conflict_zones: [optimization_layer] AGENT_L: innovation_dimension: accessibility conflict_zones: [user_interface] notes: Advanced concurrent execution with maximum sophistication - agent: parallel action: integration-preparation requires: all-waves-complete creates: merge-plan.md description: Prepare branches for integration and identify conflicts - agent: dev action: resolve-conflicts requires: merge-plan.md creates: conflict-resolution.md description: Resolve any merge conflicts between parallel work notes: May require manual intervention - agent: qa action: integration-testing requires: conflict-resolution.md validates: integration-test-suite creates: integration-test-report.md description: Test all stories work together correctly - agent: sm action: final-review requires: integration-test-report.md validates: sprint-completion-checklist creates: sprint-completion-report.md description: Review all completed stories and update statuses optional_enhancements: - agent: architect action: architecture-impact-review when: Significant architectural changes creates: architecture-impact.md description: Review how parallel changes affect overall architecture - agent: pm action: stakeholder-demo-prep when: Sprint completion creates: demo-script.md description: Prepare demonstration of completed features deliverables: required: - story-validation-report.md - dependency-analysis.md - .bmad-workspace/ck-parallel-dev/runs/{{run-id}}/pre-execution-report.md - .bmad-workspace/ck-parallel-dev/runs/{{run-id}}/execution-plan.json - .bmad-workspace/ck-parallel-dev/runs/{{run-id}}/rollback-guide.md - parallel-execution-plan.md - quality-reports-all-waves.md - integration-test-report.md - sprint-completion-report.md optional: - architecture-impact.md - demo-script.md success_metrics: efficiency: - All stories completed within sprint - Parallel execution time < sequential time / 2 - Minimal merge conflicts quality: - All DoD criteria met - Test coverage > 80% - Zero critical bugs - Linting passes innovation: - Each implementation unique - Progressive sophistication achieved - Best practices applied coordination: - Orchestrator tracks progress in JSON - Quality gates enforce standards - Context optimization for large projects - Automatic status updates risk_mitigation: - Dependency analysis prevents conflicts - Isolated worktrees prevent interference - Quality gates catch issues early - Rollback capability per story