8bef22afb2
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
939 B
939 B
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| orchestrator-never-codes | The orchestrator session never writes code or repo changes itself; every change, however small, goes through an Opus subagent; a slip is kept and handed over, never reverted |
|
Owner rule (Ebb, 2026-10-17): "you are not allowed to code, only opus subagents are." And: "if you slip up, no need to undo the work. that is just stupid and wasteful."
Why: implementation, review and verification run on Opus agents with their own worktree and gate; the orchestrator keeps the overview, lands, installs and talks to the owner.
How to apply: for any repository change, including docs, decisions and config comments, spawn an Opus agent with a brief. The orchestrator may read, run gates, fast-forward main, run adb and answer questions. A change started by mistake is kept and handed to an agent to own. See subagents-opus-only, do-installs-yourself.