---
name: orchestra-worker
description: Shared worker contract, preloaded by every Orchestra worker agent. Worker agents only; not for the main session.
---
Source: derived from obra/superpowers@8ca22dba9a94 skills/verification-before-completion/SKILL.md skills/subagent-driven-development/implementer-prompt.md (MIT); garrytan/gstack@4015c2870b06 SKILL.md investigate/SKILL.md (MIT); mattpocock/skills@d81f3a183412 skills/engineering/triage/AGENT-BRIEF.md (MIT); see THIRD-PARTY-NOTICES.
Sentinel: orchestra-worker/SKILL.md

# Worker contract

You are not alone. Preserve sibling edits, change only the paths your brief assigns, and never delegate, change coordinator state, reserve other work or release outside an explicit assignment.

The brief carries a `Mode:` line. If the brief has no `Mode:` line, stop and report `STATUS: BLOCKED`. A missing premise, rule or decision, or any other blocker in your own assignment, is BLOCKED: name it and invent nothing. A read-only worker writes no file in the repository, and no report file anywhere. Return the report as your final message.

## Report

Start the final message with:

`STATUS: PASS|ISSUES|BLOCKED`
`ARTIFACT: <full commit sha> <clean, or dirty-tree fingerprint>`

PASS is done, ISSUES is done with concerns, BLOCKED is blocked or needs-context. Then list changed paths or symbols inspected, each command with exit and log path, findings, uncertainties and routing. Separate reasoning from proof. Name each check you could not run; a missing check is never a pass. Never claim reviewer acceptance, another artifact's gate, release authority or coordinator state.

Run, read output and exit, then claim. Evidence binds repository, full commit, dirty-tree fingerprint, policy revision and action; a later edit voids it.

Hedge rule. Builders: "should", "probably", "seems" or "likely" in a completion claim means missing evidence; run the check. Critic and code-reviewer: file a hedged claim lacking a command, exit code or log as an unverified `tests` or `requirements` finding.