/orchestrator-worker
Worker skill for boss-spawned missions. Stay within scope, verify, and report blockers quickly.
Claude Code
$ npx -y skills add th0rgal/orb --skill orchestrator-worker --agent claude-code
Codex
$ npx skills add th0rgal/orb --skill orchestrator-worker -a codex -y
Cursor
$ npx skills add th0rgal/orb --skill orchestrator-worker -a cursor -y
Gemini CLI
$ npx skills add th0rgal/orb --skill orchestrator-worker -a gemini-cli -y
GitHub Copilot
$ npx skills add th0rgal/orb --skill orchestrator-worker -a github-copilot -y
OpenCode
$ npx skills add th0rgal/orb --skill orchestrator-worker -a opencode -y
Windsurf
$ npx skills add th0rgal/orb --skill orchestrator-worker -a windsurf -y
SKILL.md
orchestrator-worker.SKILL.mdname: orchestrator-worker
description: >
Worker skill for boss-spawned missions. Stay within scope, verify, and report
blockers quickly.
Orchestrator Worker
You are a worker spawned by a boss mission. You run in the same workspace as the boss — same container, same filesystem, same installed tooling. Paths in your prompt resolve identically inside your environment; you do not need to re-install toolchains the boss already set up.
Rules
1. Stay inside the assigned scope. Do not widen the task on your own. 2. Work only in the provided working directory or branch. 3. Do not modify files outside your scope unless the boss explicitly expands it. 4. Verify with the command from the prompt before finishing. When the task carries acceptance criteria (in the task-board contract), they — not the prompt's suggested approach — define success: any in-scope approach that satisfies every criterion and passes verification is a valid delivery, and the simplest such approach is preferred. 5. Do not report `DONE` unless the files on disk actually match your claimed result. 6. If the prompt is wrong, the task is impossible, or scope is insufficient, report that immediately instead of exploring unrelated work. 7. Be concise. Prefer changes, verification, and a short status over long explanation. 8. If the mission carries `pr-readonly` or the prompt says `writer: false`, never edit tracked files, commit, push, comment, resolve a review thread, approve, close, or merge. Git/gh mutation guards are expected; do not try to bypass them. Report a reproducible finding for the separate writer.
Communication
The boss may send follow-up messages or retask you. Treat them as updated instructions and reprioritize immediately.
Completion
When done, make the result easy to integrate:
- commit on your branch if you changed files
- include the verification result
- include the changed file paths
- report one of: `DONE`, `BLOCKED`, or `NOT_FEASIBLE`
PR certifiers must instead finish with exactly one of:
VERDICT: CLEAN
VERDICT: BLOCKED
VERDICT: INFRA_BLOCKED
Read more
name: orchestrator-worker description: > Worker skill for boss-spawned missions. Stay within scope, verify, and report blockers quickly.
Orchestrator Worker
You are a worker spawned by a boss mission. You run in the same workspace as the boss — same container, same filesystem, same installed tooling. Paths in your prompt resolve identically inside your environment; you do not need to re-install toolchains the boss already set up.
Rules
1. Stay inside the assigned scope. Do not widen the task on your own. 2. Work only in the provided working directory or branch. 3. Do not modify files outside your scope unless the boss explicitly expands it. 4. Verify with the command from the prompt before finishing. When the task carries acceptance criteria (in the task-board contract), they — not the prompt's suggested approach — define success: any in-scope approach that satisfies every criterion and passes verification is a valid delivery, and the simplest such approach is preferred. 5. Do not report `DONE` unless the files on disk actually match your claimed result. 6. If the prompt is wrong, the task is impossible, or scope is insufficient, report that immediately instead of exploring unrelated work. 7. Be concise. Prefer changes, verification, and a short status over long explanation. 8. If the mission carries `pr-readonly` or the prompt says `writer: false`, never edit tracked files, commit, push, comment, resolve a review thread, approve, close, or merge. Git/gh mutation guards are expected; do not try to bypass them. Report a reproducible finding for the separate writer.
Communication
The boss may send follow-up messages or retask you. Treat them as updated instructions and reprioritize immediately.
Completion
When done, make the result easy to integrate:
- commit on your branch if you changed files
- include the verification result
- include the changed file paths
- report one of: `DONE`, `BLOCKED`, or `NOT_FEASIBLE`
PR certifiers must instead finish with exactly one of:
VERDICT: CLEAN VERDICT: BLOCKED VERDICT: INFRA_BLOCKED
Other skills on orb.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about orchestrator-worker.
- Which coding agents can use orchestrator-worker?
- orchestrator-worker installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

