Cross-agent collaboration protocols, workflow handoff patterns, and commit message formats for TDD/Mikado/refactoring workflows
SkillScore91Maintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Coding pack
Last verified 8/17/2026
What it changes
Passed 20 of 22 test cases with the skill, and 10 of 22 without it.
Without skill45%
With skill91%
Checks it passed that the model alone missed
The commit body includes lines for Applied, Target, Files, and Tests.
The response specifies the tree path as "docs/mikado/<goal-name>.mikado.md".
The commit message structure includes body lines for Tree, Dependencies, and Exploration.
and 12 more in the full report
11 fixed9 passed either way1 still failing1 broke
Pass-rate lift
+45 pp
Tokens
+4%
Agent turns
0%
Response time
-42%
Model gemini-3.6-flashMeasured 8/17/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
While exploring class dependencies in a legacy reporting engine, we discovered a hidden tight coupling between ReportGenerator and LegacyDataSink. Where must the Mikado dependency tree document be stored, and how is the tree path specified in discovery commits?
What was checked, without and with the skill
Checked
Without skill
With skill
The response specifies the tree path as "docs/mikado/<goal-name>.mikado.md".
Missed
Passed
case-12 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md94 linessingle file
Collaboration and Handoffs
Cross-Agent Collaboration
Receives From
acceptance_designer (DISTILL): E2E acceptance tests | business validation requirements | production integration patterns
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
Content: complete dependency tree with annotations | true leaves with zero prerequisites | refactoring mechanics per node
Transition: Validate exploration completeness -> Confirm tree structure with proper nesting -> Activate systematic execution -> Execute leaves bottom-up using embedded refactoring knowledge -> Maintain shared progress tracking -> Ensure test-driven safety throughout
4. Integrated Workflow Patterns
tdd_with_continuous_refactoring:
pattern: "TDD -> L1-L2 Refactoring -> TDD (continuous cycle)"
timing: "After each GREEN phase in inner TDD loop"
scope: "Level 1-2 only during active TDD"
tdd_with_mikado_planning: