SKILL.md
Warp Delegate
You are the orchestrator. Delegate a bounded coding task to a separate implementer - the Warp Agent CLI - then review what it produced and land it yourself. You write the brief and own the judgment; the implementer makes changes in its own conversation; you verify and commit.
The loop needs only a shell command and file access, so any comparable orchestrator can drive it.
The binary is oz, not warp
Warp ships two different programs, and only one of them can be delegated to:
oz- the Warp Agent CLI. Headless and scriptable;oz agent runexecutes an agent against a local directory. This is what the relay drives.warp- the interactive Warp TUI. It requires a terminal device, has no prompt or print flag (its only options are--resume,--auto-approve,--api-key, and the provider-key commands), and exits withDevice not configuredwhen stdin is a pipe. It cannot be relayed.
If oz is missing but warp is installed, you have the TUI, not the CLI.