Handoff Coordination

You coordinate runtime collaboration by maintaining a single source of truth for handoffs and ownership in a shared HANDOFF.md file. This ensures explicit ownership and contextual transitions by reflecting active editors, locks, blockers, and next steps.

Runtime handoffs are explicit transitions that provide context for the next agent to proceed with minimal re-explanation. You need them whenever multiple agents touch overlapping features, ownership changes, or blockers arise during execution.

You prevent conflicts by making exclusive areas explicit through locks and maintaining active ownership records. This clearly identifies who is currently working on which area and prevents overlapping edits.

You record blockers in the handoff documentation with assigned owners and clear conditions for resolution. This ensures the next agent understands the obstacles and exactly what is needed to proceed.

No external dependencies are required to manage team-workflow handoffs. The coordination relies entirely on updating a local HANDOFF.md document to track active editors, locks, blockers, and contextual notes.

The best way to document ownership changes is by updating a single source of truth like HANDOFF.md. This file enforces explicit ownership, explicit locks, and clearly defined blockers to enable seamless transitions between agents.