agent-coordination
Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialists, managing blockers, or coordinating multi-agent workflows.
Best use case
agent-coordination is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialists, managing blockers, or coordinating multi-agent workflows.
Teams using agent-coordination should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agent-coordination/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-coordination Compares
| Feature / Agent | agent-coordination | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialists, managing blockers, or coordinating multi-agent workflows.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Agent Coordination Skill
## Purpose
Guide correct agent assignment, blocker escalation, and delivery coordination following the TDM role boundaries.
## When This Skill Applies
Invoke this skill when:
- Assigning work to specialist agents
- Managing blockers across agents
- Coordinating multi-agent workflows
- Escalating issues to ARCHitect/POPM
- Verifying pre-implementation gate
- Updating Linear with evidence
## Stop-the-Line Conditions
### FORBIDDEN Patterns
```text
# FORBIDDEN: Wrong agent assignment
Database work → BE Developer # WRONG: Use Data Engineer!
Security validation → QAS # WRONG: Use Security Engineer!
Documentation → BE Developer # WRONG: Use Tech Writer!
# FORBIDDEN: Skipping pre-implementation gate
Start coding before BSA spec # Must have acceptance criteria first
# FORBIDDEN: Unresolved blockers >4 hours
Blocker exists but not escalated # Escalate within 1 hour
```
### CORRECT Patterns
```text
# CORRECT: Right agent for the job
Database work → Data Engineer
Security validation → Security Engineer
Documentation → Tech Writer
Planning/Specs → BSA
Architecture review → System Architect
API implementation → BE Developer
UI implementation → FE Developer
Testing → QAS
PR/Release → RTE
# CORRECT: Pre-implementation gate
1. BSA creates spec with acceptance criteria
2. System Architect reviews patterns
3. THEN specialist executes
```
## Agent Assignment Matrix (MANDATORY)
| Work Type | Correct Agent | Never Use |
| ------------------- | ----------------- | ------------------- |
| Database/Migrations | Data Engineer | BE Developer |
| Security/RLS | Security Engineer | QAS |
| Documentation | Tech Writer | BE/FE Developer |
| Specs/Planning | BSA | Any implementation |
| Architecture | System Architect | Direct to developer |
| API Routes | BE Developer | FE Developer |
| UI Components | FE Developer | BE Developer |
| Testing/QA | QAS | Implementation team |
| PR/Releases | RTE | Developers |
**Reference**: `docs/workflow/TDM_AGENT_ASSIGNMENT_MATRIX.md`
## Blocker Escalation Protocol
### When to Escalate
| Condition | Escalate To | Deadline |
| ---------------------- | ----------- | ----------- |
| Blocker > 1 hour | TDM | Immediately |
| Blocker > 4 hours | ARCHitect | Urgent |
| Architecture ambiguity | ARCHitect | Before work |
| Cross-team dependency | TDM + POPM | Same day |
| Security concern | SecEng | Immediately |
### Escalation Template
```markdown
**Blocker Escalation**
**Ticket**: {TICKET_PREFIX}-XXX
**Blocked Since**: [timestamp]
**Agent**: [which specialist is blocked]
**Issue**:
[Clear description of what's blocking progress]
**Attempts Made**:
1. [What was tried]
2. [What was tried]
**Request**:
[Specific ask - decision needed, resource needed, etc.]
```
## Pre-Implementation Gate
**MANDATORY** before any implementation work:
```text
1. BSA creates spec with:
- [ ] Clear acceptance criteria
- [ ] Pattern references for execution
- [ ] Success validation command
2. System Architect reviews:
- [ ] Pattern compliance
- [ ] RLS requirements (if database)
- [ ] Security implications
3. THEN implementation can begin
```
## Evidence Attachment
All work must include evidence in Linear:
````markdown
**Implementation Evidence**
**Session ID**: [Claude session ID]
**Agent**: [which specialist]
**Ticket**: {TICKET_PREFIX}-XXX
**Work Completed**:
- [x] Task 1
- [x] Task 2
**Validation**:
```bash
yarn ci:validate
# All checks passed
```
````
**Next Steps**: [if any]
```
## TDM Boundaries
### TDM Does
- ✅ Track delivery progress
- ✅ Update Linear tickets
- ✅ Escalate blockers
- ✅ Attach evidence
- ✅ React to issues
### TDM Does NOT
- ❌ Orchestrate feature work (ARCHitect's job)
- ❌ Run CI/CD validation (specialists' job)
- ❌ Execute technical work (specialists' job)
- ❌ Proactively assign features (ARCHitect's job)
## Authoritative References
- **Agent Assignment Matrix**: `docs/workflow/TDM_AGENT_ASSIGNMENT_MATRIX.md`
- **Agent Workflow SOP v1.3**: `docs/sop/AGENT_WORKFLOW_SOP.md`
- **CONTRIBUTING.md**: Workflow requirements
- **Linear SOP skill**: Evidence attachment templates
```Related Skills
persona-coordination
Use when coordinating multi-persona team workflows, planning artifact handoffs between personas, or resolving cross-persona conflicts.
u07958-attention-management-architecture-for-eldercare-coordination
Operate the "Attention Management Architecture for eldercare coordination" capability in production for eldercare coordination workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.
bgo
Automated Blender build-go workflow. Automatically builds, removes old version, installs, enables, and launches Blender with your extension/add-on. Use when you want to quickly test changes, execute complete build-to-launch cycle, or run custom packaging scripts with automatic Blender launch.
hic-compartments-calling
This skill performs PCA-based A/B compartments calling on Hi-C .mcool datasets using pre-defined MCP tools from the cooler-tools, cooltools-tools, and plot-hic-tools servers.
heyzine-automation
Automate Heyzine tasks via Rube MCP (Composio). Always search tools first for current schemas.
heyreach-automation
Automate Heyreach tasks via Rube MCP (Composio). Always search tools first for current schemas.
HexCore Binary Analysis
Skill para analise de binarios com ferramentas HexCore integradas ao editor
here-automation
Automate Here tasks via Rube MCP (Composio). Always search tools first for current schemas.
helpwise-automation
Automate Helpwise tasks via Rube MCP (Composio). Always search tools first for current schemas.
helm-validator
Comprehensive toolkit for validating, linting, testing, and analyzing Helm charts and their rendered Kubernetes resources. Use this skill when working with Helm charts, validating templates, debugging chart issues, working with Custom Resource Definitions (CRDs) that require documentation lookup, or checking Helm best practices.
helm-generator
Comprehensive toolkit for generating best practice Helm charts and resources following current standards and conventions. Use this skill when creating new Helm charts, implementing Helm templates, or building Helm projects from scratch.
helloleads-automation
Automate Helloleads tasks via Rube MCP (Composio). Always search tools first for current schemas.