vibe-delegate

1# Vibe Delegate
2 
3You are the **orchestrator**. Hand a bounded coding task to a separate **implementer** — the Mistral
4Vibe CLI (`vibe`) — then review what it produced and land it yourself. You write the brief and own
5the judgment; Vibe does the typing in its own session; you verify and commit.
6 
7The loop needs only a shell command and file access, so any comparable orchestrator can drive it.
8 
9## When NOT to use this
10 
11- The task is small enough to do inline; delegation overhead is not worth it.
12- The `vibe` CLI is not installed or authenticated.
13 
14## Prerequisites (check once)
15 
161. Install [`uv`](https://docs.astral.sh/uv/getting-started/installation/), then Mistral Vibe:
17   - `uv tool install mistral-vibe`
182. Configure your API key with `vibe --setup`, or set `MISTRAL_API_KEY` in the environment.
193. Confirm `vibe --version` succeeds.
204. Work in, or point `--cd` at, the target git repository.
21 
22## The loop
23 
24Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.
25 
26### 1. Write the brief
27 
28Vibe sees only the text you send plus what it can inspect in the workspace — no chat history or shared
29context. Include the goal, current state, what to change, what to leave untouched, the project's
30**actual** gates, and a report contract. Tell Vibe not to commit. Keep one task per brief. See
31[references/writing-the-brief.md](references/writing-the-brief.md).
32 
33Default mode cannot approve most shell commands headlessly, so the orchestrator runs the gates. Ask
34…