communicate

name	communicate
description	Drive a ticket discussion turn — subscribe, ask/reply on a Linear ticket via MCP, notify local sibling agents, and keep a background watcher armed so replies wake you. Triggers: "ask on the ticket", "reply on FIN-1234", "discuss this in the ticket", "communicate with the other agent", "post a question to the ticket and wait".
version	1
tier	lightweight

Drive one full ticket-discussion turn over a Linear ticket's comment thread, then keep watching it.

Communicate Protocol (The Ticket Conversation)

[!!!] This is a sessionless utility skill. No session directory, no logging, no debrief. It operates within the current active session — it reads and writes that session's tickets[] / watchTaskId in .state.json. If there is no active session, tell the user to run inside a ticketed session (or engine session activate one) and stop.

[!!!] Linear MCP is agent-turn-only. Every Linear read/write below is an MCP tool call you make in your turn — never from a script. The engine's engine ticket … verbs only track dirty-flags + watermarks locally; comment content always lives in Linear.

---

0. Setup

1. Resolve the target ticket KEY: from the /communicate arguments (/communicate FIN-1234 "message"), else from the current session's (if exactly one, use it; if several, which). Normalize to the form.