omp-delegate

1# Oh My Pi Delegate
2 
3You are the **orchestrator**. Delegate a bounded coding task to a separate **implementer** - Oh My
4Pi (`omp`) - then review what it produced and land it yourself. You write the brief and own the
5judgment; the implementer makes changes 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## The binary is `omp`, not `pi`
10 
11Oh My Pi is a fork of Pi. This skill drives **`omp`** (`@oh-my-pi/pi-coding-agent`). The original
12Pi CLI is a different binary (`pi`) with a different skill (`pi-delegate`). If `omp` is missing but
13`pi` is installed, you have Pi, not Oh My Pi.
14 
15## When NOT to use this
16 
17- The task is small enough to do inline; delegation overhead is not worth it.
18- The `omp` CLI is not installed or authenticated.
19- The user asked for the original Pi CLI (`pi`) — use `pi-delegate`.
20- You need a sandboxed implementer. Oh My Pi has no sandbox. `--read-only` restricts the tool
21  surface; a write-capable run executes without prompts (`--yolo`).
22 
23## Prerequisites (check once)
24 
251. Install omp with `bun install -g @oh-my-pi/pi-coding-agent` (or the install path from
26   https://omp.sh).
272. Authenticate: `/login` inside omp for a subscription provider, or an API-key environment
28   variable for an API-key provider. Credentials live under `~/.omp/`.
293. Confirm `omp --version` succeeds.
304. Work in, or point `--cd` at, the target git repository.
31 
32## Choose the model (optional)
33…