agent-coordination

This skill acts as the operational backbone for multi-agent teams following the SAFe (Scaled Agile Framework) methodology. It provides a standardized framework for role-based task delegation, clear communication protocols, and rigorous quality gate enforcement. Designed for software engineering teams using the agentic harness, it ensures that every task is assigned to the correct specialist—such as Data Engineers for migrations or Security Engineers for RLS—preventing common errors like incorrect agent utilization or bypassed pre-implementation gates. By enforcing strict blocker escalation paths, it ensures that project delays are mitigated through immediate notification of the TDM (Technical Delivery Manager) or ARCHitect when dependencies exceed established time thresholds.

• Enforces a mandatory agent assignment matrix to prevent cross-role contamination and ensure domain-specific technical rigor.

• Manages pre-implementation gates by requiring BSA specifications, acceptance criteria, and architecture reviews before code execution.

• Automates blocker escalation protocols for blockers exceeding 1, 4, or cross-team dependency timelines.

• Provides templates for evidence attachment to Linear tickets, ensuring auditability and session-based accountability.

• Defines clear boundaries for TDM roles, preventing administrative bloat by distinguishing between coordination and technical implementation.

• Invoke this skill when assigning work, identifying cross-agent blockers, or initializing complex multi-agent workflows.

• Use the mandatory matrices for determining which agent (FE Developer, BE Developer, QAS, etc.) owns a specific work type.

• Input requirements include ticket prefixes and clear descriptions of blockers; outputs include standardized escalation logs and adherence to the pre-implementation gate checklists.

• Always ensure that work evidence is captured in the requested markdown format to maintain consistent Linear synchronization.

• Adhere to 'Stop-the-Line' conditions: never skip spec creation or wait more than one hour for critical blocker escalation.