supervisorlisted

# Supervised work Use this skill for work whose plan, decisions, or recovery must survive a session. Keep the task's scope and the owner's instructions above this process. Work that needs isolation uses a supervisor-owned worktree; root does not implement inside that worktree. ## Choose the execution mode 1. **Simple:** one Terra or Sonnet executor handles sequential work and runs the agreed checks. Root may work only in the local integration checkout when no other agent can collide with it. Isolation requires a supervisor-owned worktree, even for one sequential work package. 2. **Independent verification:** add a fresh Terra or Sonnet verifier when the change affects concurrency, persistent data, auth, public contracts, destructive operations, money, GUI/accessibility, or when tests do not convincingly observe the acceptance criteria. Give it the task, artifact, and checks without the implementer's self-assessment. 3. **Parallel:** use a Terra or Sonnet coordinator for isolated work or genuinely independent packages with distinct file ownership. Resolve shared interfaces first. Mechanical searches may use Luna or Haiku. Record the reason for each extra agent. Model class alone does not trigger a verifier. Strong Sol or Opus resolves architecture conflicts and difficult diagnosis; routine execution and coordination use cheap models. When a strong planning session has approved a task, checkpoint it and start a fresh cheap execution session instead of keeping the strong pla