Cross-Team Handoffs

Your agent creates linked handoff tasks between teams, records dependencies in notes, and drafts escalation messages for you to send. It never claims to notify anyone.

Used by our operations team

What It Does

When work on one team needs something from another, this skill creates a linked handoff task on the receiving team, notes the link on both sides, and keeps the priority aligned. It spots stalled handoffs and cross-team blockers in the tracker, and tells you about them.

It does not notify anyone. Escalation means a note in the tracker and a short message drafted for you to send to your escalation contact. For work spanning three or more teams, it sets up an initiative tag and reports on it.

Who Uses It

Team leads and coordinators whenever a task depends on another team.

Setup

1. Install and set up task-ops first. This skill requires it. Follow its backend/SETUP.md.
2. Copy the skill/ folder into your agent's skills folder as cross-team-ops, for example .claude/skills/cross-team-ops/. Or fetch it through the Thinqmesh MCP server.
3. In task-ops, edit references/team-config.md: your teams, team leads and escalation contact.
4. Make sure TASK_OPS_URL and TASK_OPS_KEY are set, as described in the task-ops setup.
5. Edit the handoff table in this skill's SKILL.md to match the handoffs your teams really have.

Example Result

Proposed handoff

New task on Engineering
  [Handoff] Implement new signup form
  owner    lead-eng@example.com   priority P1   stage Define   status Backlog
  notes    Handoff from Design #14. Needed: build the approved signup layout.

Change to Design #14 notes
  + Handed off to Engineering (ID assigned on creation)

Create these?

How to Adapt

• Replace the handoff patterns with your own teams and the point at which each handoff starts.
• Change the escalation conditions to match your service levels.
• Name your own initiative tag convention in task-ops's references/team-config.md.