agent-coordination
Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialists, managing blockers, or coordinating multi-agent workflows.
- License 许可
- MIT
- 最近更新
- 2026-10-18
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- agent-coordination
- description
- Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialists, managing blockers, or coordinating multi-agent workflows.
02 资源文件 1
- 参考文档README.md1.6 KB
03 SKILL.md 正文
Agent Coordination Skill
Purpose
Guide correct agent assignment, blocker escalation, and delivery coordination following team role boundaries.
When This Skill Applies
- Assigning work to specialist agents
- Managing blockers across agents
- Coordinating multi-agent workflows
- Escalating issues
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 |
Pre-Implementation Gate
MANDATORY before any implementation:
- BSA creates spec with acceptance criteria
- System Architect reviews patterns
- THEN implementation can begin
Blocker Escalation Protocol
| 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 |
Reference
- Agent Assignment Matrix:
docs/workflow/TDM_AGENT_ASSIGNMENT_MATRIX.md - Agent Workflow SOP:
docs/sop/AGENT_WORKFLOW_SOP.md
04 同仓库更多 Skills
stripe-patterns
暂无简介
payment-patterns
暂无简介
testing-patterns
Testing patterns for Jest and Playwright. Use when writing tests, setting up test fixtures, or validating RLS enforcement. Routes to existing test conventions.
team-coordination
Agent Teams orchestration patterns for multi-agent SAFe workflows. Use when spawning agent teams, coordinating teammates, enforcing quality gates via task dependencies, or orchestrating the 11-agent SAFe pipeline. Covers team creation, messaging, shared task lists, and SAFe gate enforcement. Do NOT use for single-agent or simple subagent workflows.
task-compilation
Compile broad audit goals into structured proof obligations with 9 mandatory fields. Used after decomposition by the Threat Modeler agent.
storage-layout-analysis
Proxy patterns, slot collisions, upgrade safety. Used during decomposition to identify storage-related vulnerabilities in upgradeable contracts.