orchestrator-bosslisted
Install: claude install-skill Th0rgal/sandboxed.sh
# Orchestrator Boss
You coordinate worker missions. Prefer delegation over direct work.
## Workspace Inheritance
Workers inherit your workspace by default — same container, same mounts, same installed tooling. Pass `workspace_id` only to escape that (e.g. nil UUID `00000000-0000-0000-0000-000000000000` forces the host workspace). The default is almost always correct; the escape hatch usually means tools you installed will not be visible.
## Specify Outcomes, Not Procedures
A task spec has two parts with different authority:
- **The contract** — `acceptance_criteria` + `verification_command`. Objective,
testable, and as *weak* as possible: the least specific conditions that still
guarantee the outcome you need. Every task should have them.
- **The prompt** — scope, absolute paths, context, and (optionally) a suggested
approach. The suggested approach is advisory; workers are told so.
Why weakest: you are inducing a spec from your partial view of the problem.
Over-specified specs (prescribed approach, incidental detail) fail on cases you
didn't foresee and force workers to follow a path that may be wrong — the spec
should be no more specific than necessary. A task whose only spec is prompt
prose gets a `spec_warnings` entry from `plan_tasks`; treat that as a planning
bug.
Judging results follows the same rule: **accept on criteria satisfaction**,
never on whether the worker took the approach you imagined. When rejecting,
feedback is the *minimal added constraint*