Skip to content

03 workflows parallel development

Jump to bottom
Doug Beard edited this page Aug 21, 2025 · 2 revisions

Parallel Development - Coordinated Execution Patterns

Overview

Coherence APM Framework v4.2.0 provides coordinated execution capabilities through 6 actual parallel commands, enabling unified context engineering across multiple workflow streams. This workflow maximizes development coordination through intelligent parallel execution.

🚀 Coherence Parallel Architecture

Coordinated Execution Features

Coherence APM Framework v4.2.0 provides coordinated execution through:

  • 6 Parallel Commands: Actual available parallel commands for specific workflows
  • Unified Context Engineering: Consistent context preservation across parallel streams
  • Session Management: Persistent context in .apm/session_notes/ directory
  • Voice Notifications: Audio feedback for parallel command execution

Available Parallel Commands

The framework provides 6 actual parallel commands:

  • /planning-stories: Batch story creation and planning
  • /qa-framework: Comprehensive testing setup and validation
  • /qa-regression-suite: Coordinated test execution and validation
  • /planning-next-story: Sprint continuation and story progression
  • /qa-acceptance-criteria: Quality validation and acceptance testing
  • /planning-checklist: Coordinated verification and validation

🎯 When to Use Parallel Commands

Perfect Use Cases

✅ Use Parallel Commands For:

  • Story Planning: Use /planning-stories for batch story creation
  • QA Setup: Use /qa-framework for comprehensive testing coordination
  • Regression Testing: Use /qa-regression-suite for coordinated test execution
  • Sprint Continuation: Use /planning-next-story for efficient story progression
  • Acceptance Validation: Use /qa-acceptance-criteria for quality validation
  • Checklist Coordination: Use /planning-checklist for verification workflows

❌ Avoid Parallel Commands For:

  • Simple Tasks: Single component changes better handled by individual personas
  • Learning/Exploration: Discovery work requiring sequential investigation
  • Heavy Dependencies: Work requiring strict sequential execution
  • Small Changes: Work that can be completed by single persona efficiently

🏗️ Parallel Command Patterns

Pattern 1: Story Planning Coordination

/planning-stories → Coordinated story creation and acceptance criteria

When to Use: Batch story creation for sprint planning Benefits: Unified context across story development Coordination: Consistent story format and acceptance criteria

Example - Sprint Story Creation:

  • Coordinated Planning: Multiple stories created with unified context
  • Acceptance Criteria: Consistent quality standards across stories
  • Context Preservation: Session notes maintain planning decisions
  • Voice Feedback: Audio confirmation of story creation completion

Pattern 2: QA Framework Setup

/qa-framework → Coordinated testing setup and validation

When to Use: Comprehensive testing framework establishment Benefits: Unified testing approach across components Coordination: Consistent test patterns and quality standards

Example - Testing Infrastructure:

  • Test Strategy: Coordinated approach to testing methodology
  • Framework Setup: Unified testing tools and configurations
  • Quality Standards: Consistent validation criteria across tests
  • Documentation: Session notes capture testing decisions

Pattern 3: Regression Testing Coordination

/qa-regression-suite → Coordinated test execution and validation

When to Use: Comprehensive regression testing across system components Benefits: Unified test execution with coordinated validation Coordination: Consistent test result reporting and issue tracking

Example - System Validation:

  • Test Execution: Coordinated execution of regression test suites
  • Result Analysis: Unified analysis of test outcomes
  • Issue Tracking: Consistent tracking of test failures and fixes
  • Quality Gates: Coordinated validation of system quality

Pattern 4: Sprint Continuation Planning

/planning-next-story → Coordinated next story identification and planning

When to Use: Efficient transition to next stories in sprint workflow Benefits: Seamless continuation of sprint momentum Coordination: Unified context for story progression and priority management

Example - Sprint Flow:

  • Story Progression: Coordinated identification of next priority stories
  • Context Transfer: Seamless handoff of completed work to next stories
  • Priority Alignment: Unified understanding of story priorities
  • Planning Efficiency: Reduced overhead in story transition

🎪 Coherence Parallel Command Portfolio

Available Parallel Commands (6 Total)

/planning-stories - Batch Story Creation

Purpose: Coordinated story creation and planning

  • Function: Creates multiple user stories with unified context
  • Benefits: Consistent story format and acceptance criteria
  • Integration: Updates session notes and maintains planning context
  • Voice Feedback: Audio confirmation of story creation completion

Prerequisites:

  • Epic or feature requirements defined
  • Clear understanding of user needs
  • Access to project documentation

/qa-framework - Testing Framework Setup

Purpose: Comprehensive testing framework establishment

  • Function: Coordinates testing setup across multiple components
  • Benefits: Unified testing approach and quality standards
  • Integration: Session notes capture testing decisions and frameworks
  • Voice Feedback: Audio confirmation of framework setup

/qa-regression-suite - Coordinated Test Execution

Purpose: Comprehensive regression testing coordination

  • Function: Executes and coordinates regression test suites
  • Benefits: Unified test result analysis and issue tracking
  • Integration: Updates test results in session notes
  • Voice Feedback: Audio notification of test completion

/planning-next-story - Sprint Continuation

Purpose: Efficient transition to next stories in workflow

  • Function: Coordinates next story identification and planning
  • Benefits: Seamless sprint momentum and context preservation
  • Integration: Maintains sprint context in session notes
  • Voice Feedback: Audio confirmation of story transition

/qa-acceptance-criteria - Quality Validation

Purpose: Coordinated acceptance criteria validation

  • Function: Validates quality standards across multiple criteria
  • Benefits: Consistent quality validation and sign-off tracking
  • Integration: Documents validation results in session notes
  • Voice Feedback: Audio confirmation of validation completion

/planning-checklist - Coordinated Verification

Purpose: Systematic verification and validation coordination

  • Function: Coordinates checklist-based verification processes
  • Benefits: Comprehensive verification with unified standards
  • Integration: Maintains verification status in session notes
  • Voice Feedback: Audio confirmation of checklist completion

Additional Workflow Integration

The 6 parallel commands integrate with other Coherence workflows:

Integration with Planning Workflows

  • Story Planning: /planning-stories coordinates with /po and /sm personas
  • Checklist Validation: /planning-checklist supports systematic verification
  • Next Story Flow: /planning-next-story maintains sprint momentum

Integration with QA Workflows

  • Framework Setup: /qa-framework establishes testing foundations
  • Acceptance Validation: /qa-acceptance-criteria ensures quality standards
  • Regression Testing: /qa-regression-suite provides comprehensive validation

Session Management Integration

  • Context Preservation: All parallel commands maintain context in .apm/session_notes/
  • Voice Notifications: Audio feedback confirms completion of parallel operations
  • Unified Documentation: Session notes capture parallel workflow decisions and outcomes

🔄 Parallel Command Execution Workflow

1. Parallel Command Initiation

# Example: Launch parallel story planning
/planning-stories

What Happens Internally:

  1. Command Recognition: Coherence identifies parallel execution request
  2. Context Loading: Loads unified context from session notes and project documentation
  3. Coordination Setup: Establishes shared context and communication channels
  4. Execution Coordination: Coordinates parallel workflow execution
  5. Session Documentation: Updates session notes with parallel execution results

2. Unified Context Coordination

Coordination Features:

  • Shared Context: All parallel operations access unified project context
  • Session Integration: Automatic updates to .apm/session_notes/ directory
  • Voice Notifications: Audio feedback confirms coordination milestones
  • Documentation Preservation: Context maintained across parallel operations

3. Coordinated Execution Management

Parallel Operation Management:

  • Workflow Coordination: Operations coordinate through unified context
  • Quality Standards: Consistent quality validation across parallel operations
  • Error Handling: Graceful handling of issues within parallel workflows
  • Context Preservation: Unified context maintained throughout execution

4. Results Integration & Documentation

Completion Process:

  • Result Synthesis: All parallel operations contribute to unified outcome
  • Quality Validation: Final validation of coordinated results
  • Session Documentation: Comprehensive update of session notes with results
  • Voice Confirmation: Audio notification of successful completion

📊 Workflow Benefits & Coordination

Coordination Benefits

Unified Context Engineering

  • Consistent Context: All parallel operations maintain unified project context
  • Session Continuity: Persistent documentation in .apm/session_notes/ directory
  • Voice Integration: Audio feedback provides workflow confirmation
  • Quality Standards: Consistent quality validation across parallel operations

Workflow Efficiency

  • Reduced Context Switching: Coordinated operations minimize persona transitions
  • Systematic Approach: Structured workflows with defined coordination patterns
  • Documentation Quality: Comprehensive session notes capture parallel workflow decisions
  • Integration Points: Clear handoff and coordination between parallel operations

Quality Improvements

  • Systematic Validation: Coordinated quality checks across multiple workflow aspects
  • Consistent Standards: Unified quality criteria applied across parallel operations
  • Comprehensive Coverage: Multiple validation streams ensure thorough quality review
  • Documentation Integrity: Session notes maintain complete workflow history

🚨 Parallel Development Best Practices

✅ Do These Things

1. Plan for Parallelism

  • Decompose Features: Break down work into independent components
  • Document Dependencies: Clear dependency mapping in backlog.md
  • Define Integration Points: Specify when parallel streams must synchronize
  • Allocate Capacity: Ensure team has capacity for parallel work

2. Optimize for Native Sub-Agents

  • Use Parallel Commands: Default to /parallel-* commands for multi-component work
  • Trust Coordination: Let native sub-agents handle dependency resolution
  • Monitor Progress: Use session notes for progress tracking
  • Validate Integration: Regular integration testing throughout development

3. Maintain Quality Standards

  • Parallel Testing: Include testing streams in all parallel development
  • Code Reviews: Review code from all parallel streams
  • Integration Validation: Test integrated components thoroughly
  • Documentation: Keep session notes current across all streams

❌ Avoid These Mistakes

1. Over-Parallelization

  • Don't Parallelize Simple Work: Use sequential execution for simple tasks
  • Don't Ignore Dependencies: Respect true dependencies between components
  • Don't Over-Allocate: Don't use more sub-agents than optimal (2-4)

2. Under-Coordination

  • Don't Skip Integration Testing: Always validate parallel work integration
  • Don't Neglect Communication: Keep all streams informed of changes
  • Don't Ignore Conflicts: Address integration conflicts immediately

3. Documentation Lapses

  • Don't Skip Session Notes: Document progress from all parallel streams
  • Don't Forget Backlog Updates: Update backlog.md with parallel work progress
  • Don't Skip Handoff Documentation: Document work for future sessions

🎯 Parallel Development Decision Tree

Step 1: Assess Work Complexity

Is this work:
├── Simple (< 2 hours, single component) → Use sequential development
├── Medium (2-6 hours, 2-3 components) → Consider parallel development  
└── Complex (> 6 hours, 3+ components) → Use parallel development

Step 2: Evaluate Dependencies

Are components:
├── Highly Dependent → Sequential development (with parallel testing)
├── Moderately Dependent → Parallel with frequent integration points
└── Independent → Full parallel development

Step 3: Check Team Capacity

Team capacity:
├── Limited (1-2 developers) → Sequential with parallel QA
├── Moderate (3-4 developers) → 2-3 parallel streams
└── High (5+ developers) → 3-4 parallel streams

Step 4: Select Parallel Pattern

Choose pattern based on:
├── Feature Work → /planning-stories or /implementation-sprint
├── Architecture Work → /planning-architecture  
├── Testing Work → /parallel-test-plan or /qa-framework
├── Infrastructure Work → /parallel-automation-plan
└── Problem Solving → /parallel-course-correction

🛠️ Advanced Coordination Strategies

Strategy 1: Dependency-Aware Coordination

Automatic Dependency Resolution:

  • Native sub-agents automatically detect and resolve integration dependencies
  • Real-time coordination prevents conflicts before they occur
  • Intelligent work sequencing within parallel streams

Strategy 2: Progressive Integration

Incremental Integration Points:

  • Regular integration checkpoints throughout parallel development
  • Continuous validation of integrated components
  • Early detection of integration issues

Strategy 3: Resource-Aware Scaling

Dynamic Sub-Agent Management:

  • Automatic scaling of sub-agents based on work complexity
  • Resource optimization to prevent system overload
  • Intelligent workload distribution across available sub-agents

📈 ROI & Business Impact

Development Velocity Impact

  • Story Completion Rate: 250-400% improvement for complex features
  • Epic Delivery Time: 300-600% improvement for large initiatives
  • Time to Market: Significant reduction in feature delivery timelines

Quality Improvements

  • Defect Reduction: Parallel testing streams improve quality
  • Test Coverage: Specialized testing streams increase coverage
  • Architecture Consistency: Parallel design validation improves consistency

Team Productivity

  • Developer Satisfaction: Reduced waiting time and context switching
  • Focus Quality: Each sub-agent focuses on specialized area of expertise
  • Learning Acceleration: Parallel work exposes developers to broader system

Business Value

  • Faster Feature Delivery: Competitive advantage through speed
  • Higher Quality Products: Better testing and validation
  • Reduced Development Costs: More efficient resource utilization

📚 Integration with Other Workflows

Combine with Session Management

  • Continuous Documentation: Session notes from all parallel streams
  • Context Preservation: Maintain context across parallel sessions
  • Handoff Coordination: Smooth transitions between parallel and sequential work

Combine with Team Collaboration

  • Multi-User Coordination: Multiple team members working on parallel streams
  • Communication Protocols: Keep all team members informed of parallel progress
  • Conflict Resolution: Team-based resolution of parallel development conflicts

Combine with Backlog Management

  • Parallel Story Updates: Update backlog.md with progress from all streams
  • Acceptance Criteria Tracking: Track criteria completion across parallel work
  • Sprint Health Monitoring: Monitor sprint progress with parallel execution

📚 Related Documentation

Harness the power of native sub-agent parallelism for revolutionary development performance.

Clone this wiki locally