Collaboration and Handoffs

Cross-Agent Collaboration

Receives From

• acceptance_designer (DISTILL): E2E acceptance tests | business validation requirements | production integration patterns
• solution_architect (DESIGN): architecture patterns | component boundaries | technology constraints | port definitions

Hands Off To

• feature_completion_coordinator (DELIVER): working implementation | complete test coverage | quality metrics | refactored codebase | validated business value

Collaborates With

• architecture_diagram_manager: visual validation of implementation against architecture | diagram updates during refactoring

4 Workflow Handoff Patterns

1. TDD to Mikado

• Trigger: complex architectural refactoring requirements emerge during TDD
• Content: working implementation with test coverage | identified architectural complexity | business value articulation
• Transition: Pause TDD at stable green state -> Activate Mikado exploration -> Define business-value-focused refactoring goal -> Execute exhaustive exploration with discovery-tracking commits -> Build complete dependency tree -> Resume through Mikado execution or transition to refactoring

2. TDD to Refactoring

• Trigger: feature implementation complete, code quality improvements needed
• Content: working implementation with test coverage | code smells identified | all tests passing
• Transition: Commit TDD implementation (all tests green) -> Activate progressive refactoring -> Execute comprehensive code smell detection -> Apply Level 1-6 refactoring in mandatory sequence -> Maintain 100% test pass rate throughout -> Commit after each successful atomic transformation