minutes-copilot

1# /minutes-copilot
2 
3Use the real Minutes copilot runtime to start or control Coach. Do not build a transcript reader, event poller, prompt loop, or shell tailer in this skill.
4 
5If the user explicitly asks **you or the current terminal agent** to watch, advise, or strategize, use `/minutes-live-sidekick` instead. If the user says only "coach me live" or otherwise leaves the surface ambiguous, ask exactly: "Do you want me in this terminal to be your sidekick, or should I open the Minutes Coach HUD?" Do not start Coach while clarifying.
6 
7## Start Coach
8 
91. Get one concrete meeting goal. Use the user's stated goal; if none is present, ask exactly: "What outcome should Coach help you achieve in this meeting?"
102. Choose a supported mode only when the user makes it clear: `sales`, `discovery`, `interview`, `negotiation`, `difficult-conversation`, `decision`, or `generic`. Default to `generic`.
113. If first-party Minutes copilot MCP controls are actually available, call their start control with the same goal, mode, and `tui` surface. Never invent an MCP tool name.
124. Otherwise invoke the foreground CLI, passing the goal as one safely escaped argument:
13 
14```bash
15minutes copilot start --goal '<meeting goal>' --surface tui --mode generic
16```
17 
18The `tui` surface is the Coach HUD. Keep the command attached as the live session. Add `--live` only when the user explicitly asks Coach to own a standalone capture; normally Coach attaches to the existing Minutes capture stream.
19…