agent-coordination

Agent assignment uses a matrix that routes tasks to the right specialists based on their role. Define which agents handle data engineering, architecture, product ownership, and other functions, then attach task details to Linear tickets specifying the assigned agent and expected turnaround.

Blocker escalation follows a protocol with clear paths and deadlines. Flag blockers immediately in Linear, assign them to the appropriate escalation level (ARCHitect, POPM, or specialist), document the blocker reason, and attach supporting evidence to trigger resolution within SLA.

Pre-implementation gating captures acceptance criteria and review sign-offs before coding begins. Attach evidence blocks to Linear tickets documenting requirements, design review approvals, and stakeholder acceptance, preventing rework and maintaining quality across team deliverables.

Yes. Evidence attachment embeds design documents, test results, approval records, and status updates directly into Linear tickets, creating an audit trail and enabling ARCHitect and POPM to review and approve work without context-switching between tools.

TDM boundaries clarify which decisions and tasks belong to the technical delivery manager versus specialist agents. Defining these prevents duplication, speeds escalation, and ensures the right person owns each decision—reducing delays when blockers arise.

Multi-agent coordination synchronizes task delegation, blocker escalation, and evidence capture across teams using the agent assignment matrix and shared Linear tickets. This maintains momentum by ensuring blockers surface quickly and specialists receive clear priorities and dependencies.