orchestrate
Skill1 starsChanged yesterdayMITView on GitHub
Turn the owner's feature or problem into an approved plan across tickets, keep its state in the workbench, and run it to an announced close.
173 other projects use a version of this.
Adopted by
Most recently taken up by
- chengzi-io/piertheir own version, first seen Nov 16, 2026
- endqwerty/endstacktheir own version, first seen Nov 16, 2026
- ddivyanshsharmaa/fable-toolkittheir own version, first seen Nov 16, 2026
- ronedgecomb/anythingtheir own version, first seen Nov 16, 2026
- MithunWijayasiri/dotclaudetheir own version, first seen Nov 16, 2026
- nickthelegend/nick-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use define-requirements, orchestrate-plan and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
sson0-erSkilldefine-requirements
Work with the user, one question at a time, to complete the requirements document (docs/claudex/<slug>/01-requirements.md). Run by the orchestrator (parent). Stays out of design and implementation.
Also in 3 projects that use this
EternallLightSkillorchestrate-plan
Use when executing a locked, reviewed PLAN.md by delegating the implementation to visible worker agents in Orca, herdr, or cmux ONE PHASE at a time — splitting the plan into context-window-sized phases, giving every phase a pristine worker context, and (when the plan touches INDEPENDENT repos) running one worker per repo IN PARALLEL. Triggers on "run the plan with a worker", "execute the plan in the other pane", "split the plan into phases and build it with workers", "build the backend and frontend in parallel panes". Not for edits you can finish inline; outside Orca, herdr, or cmux use tgc-skills:orchestrate.
Also in 3 projects that use this
sson0-erSkillrecord-evidence
How to record external facts (docs, command output, codebase findings) as evidence and design choices as decisions. Used by the researcher, designer and reviewer agents.
Also in 3 projects that use this
PinkneyJiangSkillimprove-architecture
扫描代码库中的架构摩擦点,识别浅模块并挖掘深模块演进机会。生成可视化交互式 HTML 诊断报告,并在用户确认后闭环实施深度重构。
Also in 4 projects that use this
kjnezSkillticket
Work on a JIRA/Linear ticket end-to-end: read ticket details, explore codebase, create a branch, implement with TDD, run quality checks, update ticket status, and create a PR. Use when the user provides a ticket ID to implement. Triggers on requests like "/ticket PROJ-123", "work on this ticket", "implement PROJ-123".
Also in 4 projects that use this
mukcoSkillprinciples
General software engineering principles — DRY, SOLID, YAGNI, KISS, naming, code smells, and refactoring. Language-agnostic. Use alongside language-specific skills.
Also in 3 projects that use this
Other versions173 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 173
- Significant-Gravitas/AutoGPT★ 188ksame name
- expo/exact★ 4.3ksame name
- rohitg00/pro-workflow★ 2.9ksame name
- apmantza/pi-lens★ 530same name
- boshu2/agentops★ 454same name
- quantumaikr/quant.cpp★ 403same name
- Noizefield/audio-plugin-coder★ 334same name
- kagenti/kagenti★ 304same name
- varun29ankuS/shodh-memory★ 294same name
- provencher/codex-skills★ 271same name
163 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- babysitSkill
- codebase-designSkill
- code-reviewSkill
- create-adopted-repoSkill
- create-repositorySkill
- diagnosing-bugsSkill
- domain-modelingSkill
- factorySkill
- grillingSkill
- grill-with-docsSkill
- implementSkill
- improve-codebase-architectureSkill
- prototypeSkill
- prSkill
- repository-standardsSkill
- researchSkill
- retroSkill
- reviewSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wayfinderSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 155 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Follow each repository's CONTRIBUTING.md for triage, readiness, questions, findings and delivery, and installed comment rules for posts.
- Distinctive: line 15
Read templates before you write a workbench file, launches before you launch, take over, hand over, observe or arm a wait, and close before …
- Very specific: line 37
Use the Canonical stages in the repository's installed factory-workflow rules (source: rules/factory-workflow.md).
- Very specific: line 48
Keep Item | Running | Waiting on owner | Since (UTC) | Next check.
- Very specific: line 63
Read intake for ideas, state:grill issues, retro/architecture reports, or questions from launch reports, issues or incoming messages.
- Distinctive: line 69
Keep deferrals at their code.
- Distinctive: line 79
When all rows end, close: reconcile issues, run Close reviews and announce the close.
- Distinctive: line 83
Keep one background wait continuously armed during foreground work and between turns, covering every In-flight wake mechanism, launch …
- Distinctive: line 86
Use harness events for what the script cannot observe.
- Distinctive: line 110
Create missing files as templates says.
- Distinctive: line 113
When it is missing, use the example source.
“Common” is measured: kept by at least 6 in 10 of the 155 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
A prompt or brief naming this skill is its invocation.
Orchestrate
Follow each repository's CONTRIBUTING.md for triage, readiness, questions, findings
and delivery, and installed comment rules for posts. triage handles one request;
factory delivers factory tickets and held, stopped or skipped work.
Read templates before you write a workbench file,
launches before you launch, take over, hand over,
observe or arm a wait, and close before you close a plan.
Apply codebase-design's Ownership check to your inbox recommendations, plan updates and friction.
Workbench
The workbench is a private Markdown git repository outside projects. Use the path in your global instructions, or create one before proposing a plan. Commit straight to its default branch; push if it has a private remote. Repository issues, briefs, comments and decision records must be self-contained: copy every relied-on decision, with its date and quoted words, even when duplicated. Never reference or require the private workbench from a repository: no URL, host path or instruction to consult it as input or provenance. Repository records may cite each other; private planning retains its own sources. Its files:
index.md: repositories, plans, the current owning session.inbox.md: decisions; reconcile and process answers before other work.wishes.md: ideas outside the goal;now.md: current state, rewritten each pass.incoming/: other sessions' messages.<plan>/: currentplan.md, append-onlylog.md, decision and run records.
Lifecycle
Use the Canonical stages in the repository's installed factory-workflow
rules (source: rules/factory-workflow.md). Read coverage with .scriptorium/config.json. <!-- Seam (deferred): Scriptorium configuration reads; consumers: 6; extraction proposed in https://github.com/lutzseverino/repo-canon/issues/967. -->
For each covered stage hand off through factory and wait; otherwise perform it
by hand to the same contract with the factory's own scripts. When recording its
launch in now.md, log Gap | <stage> | <repository> | <why> in log.md.
Intake of ideas is permanent orchestrating work, exempt from gap logging;
intake owns its method.
A plan update includes proposals and heartbeat replies. Open with
wait.mjs --status --from <now.md>, adding --budget <status.json> for the
Scriptorium observation from launches.
Keep Item | Running | Waiting on owner | Since (UTC) | Next check; read only
records/budget, never harness thread lists or a second view. In this update, act
on each your move row or turn it into a real wait: launch, factory, owner,
named third party or date. Show arrivals as templates says,
the inbox and every choice made alone since the last update, with dated sources for veto; log each.
Link every row/decision code and issue number to its row, record or issue;
expand unfamiliar codes once per owner-facing message. Deferred checker: implement over
now.md, inbox.md and plan.md only at the first recorded post-release bare-code slip.
Present goal, Done means, specifications, tickets and Close reviews for approval; record proposal and approval before execution. Research, filing and contract preparation may precede it; execution readiness waits for approval, which replaces no independent review or readiness condition. An owner's request for work now skips only the plan: Expedited change.
Read intake for ideas, state:grill issues, retro/architecture
reports, or questions from launch reports, issues or incoming messages. After a grill, retain the
contribution guide's writer publication, final split and independent acceptance
responsibilities; use to-spec and to-tickets through the launch template.
Log friction with evidence, Value owner, exposed seam and route (row, finding or wish). Keep deferrals at their code. Route Findings under the guide even outside the goal without waiting for resolution. A new requirement mid-plan, unless wanted now, takes:
- Row: serves the goal and passes the guide's inference test; add and log a row, and list it in the next update.
- Amendment: changes goal or scope; grill it, possibly one round in the orchestrating thread. Apply only after owner approval, with a new approval line superseding the old, and publication under the contribution guide.
- Wish: outside the goal and not a Finding; add to
wishes.md, needing no issue.
When all rows end, close: reconcile issues, run Close reviews and announce the close.
The wait step
Keep one background wait continuously armed during foreground work and between turns, covering every In-flight wake mechanism, launch report and incoming message. Owner-only rows use recorded owner waits and incoming responses; with no work, wait on incoming. Use harness events for what the script cannot observe. On wake/timeout, minimally reconcile expected facts and records, then immediately re-arm before other work or updates. Rewrite records to change watches. Without background waits or events, report the limit and reread records each turn.
Report-back
Launches hand back only through their current-turn report, final line status: done:
“this turn ended; read the report”, including owner waits, never success. Follow
launches for prerequisites/relay and consume reports.
Other sessions write to incoming/.
Reads
Paths are relative to each repository or the workbench.
CONTRIBUTING.mdand.repo-standards/rules/comments.md: the sections and comment rules named above. When either is missing, carry out this method as written, and put each rule it leaves to it ininbox.mdfor the owner.AGENTS.md: delegation, naming and workstation convention. If missing, pass context only and name sessions for operation/target where naming is supported.- The
codebase-designskill: Ownership check. If missing, file the gap under Findings; retain the fields above. - The workbench, whose format this skill owns: its
index.md,inbox.md,wishes.md,now.md,inbox-archive.md,incoming/,<plan>/plan.md,<plan>/log.mdandretro.md. Create missing files as templates says. - A tracked repository's Repository Standards adoption record: the Repo Canon
source its Selection names, for the
workbenchprofile offer. When it is missing, use the example source. .repo-standards/rules/factory-workflow.mdand.scriptorium/config.json: stages, coverage and Model selection. When configuration is missing, do uncovered work by hand; when rules are missing, consult sourcerules/factory-workflow.mdfor the stages.- Scriptorium status JSON: budget/model observations. When absent or unavailable, report missing facts and establish them before launching.
- The
retroskill: method and lesson routes. When missing, obtain it before closing the plan. - The
babysitskill: the wait's GitHub CLI connection and merge continuation. When missing, re-read records each turn as the wait step says.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

