minutes-x1-closeout

1# /minutes-x1-closeout
2 
3Turn one clear meeting outcome into a proposed closeout for one existing X1
4coordination thread. Minutes supplies the source. X1 supplies identity,
5authority, review, disposition, and the household record.
6 
7## Required connections
8 
9This workflow needs both the local Minutes MCP and the official X1 MCP. If X1
10isn't connected, stop after identifying the meeting outcome and direct the user
11to X1's official connection instructions. Don't invent an endpoint, credential,
12account, thread ID, or local substitute.
13 
14## Workflow
15 
161. Call Minutes `get_meeting_insights` with `include_restricted: false` to find
17   an `explicit` or `strong` decision or commitment that supports the closeout
18   the user requested. The logged restricted-source override is forbidden for
19   this cross-service handoff. Use only an insight released by that bounded
20   call. Don't use `agent.annotation`, a raw path, a transcript fragment read
21   outside Minutes, or a model-written summary as source proof.
22 
232. Use X1 `find_coordination_threads` or `list_my_coordination_threads`, then
24   `get_coordination_thread`, to resolve exactly one open thread the signed-in
25   X1 actor can read. If zero or multiple threads plausibly match, ask the user
26   to choose. Never select a hidden, closed, or guessed target.
27 
283. Ask the user to choose the X1 outcome if they haven't already:
29   `resolved`, `escalated_elsewhere`, `deferred`, or `no_longer_relevant`.
30…