Use when handed a batch of delivery documents to drive to done in one run -- several IDs to build, ordered by their dependency edges, each with review, commit, and status transitions, until the whole batch is done.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
```
YOU ORDER, DISPATCH, REVIEW, COMMIT, CLOSE. YOU DO NOT BUILD.
```
Orchestrate drives a **chunk** -- the set of delivery documents you were handed -- to done. You own ordering, dispatch, review, commits, status transitions, and the done check. Each unit's building is a dispatched agent's, running /execute.
The chunk is whatever set you were given. It may span several parent documents, or sit under one. Nothing here assumes a type name; read every type, relation, and status from `lazyspec config --json`.
**REQUIRED SUB-SKILLS:** /execute (loaded by each build agent), /review-work (both passes), /advance (every status move).
<HARD-GATE>
**Depth 1. You are the only agent that spawns agents.** Every agent you dispatch does its own work alone. Check each dispatch against the fan-out table before you send it; if it is not a row, you do not need it.
**Never `sleep` to wait for an agent.** You are re-invoked when it finishes. Dispatch, then end your turn. That is the whole protocol.
Do NOT build, edit, or fix anything yourself. Dispatch it.
Do NOT re-run the gate command to confirm what an agent reported.
…
The line at the top of this page pins the label git:20260903.f1f85b0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (12580 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
jkaloger/lazyspec · 10 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tx25gfgvqmvt645w
GET https://markdownregistry.com/api/v1/resolve?ref=jkaloger/lazyspec/orchestrate
GET https://markdownregistry.com/api/v1/blob/1a3843c15ceeb8576ae9fd43111e74c920572a32e69384a3f60c2c5929a25dc8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
jkaloger/lazyspec · examples/spec/skills/create-plan/SKILL.md · Use when planning implementation against a Spec or as a standalone plan for bug fixes, tweaks, and refactors. Creates…
jkaloger/lazyspec · examples/spec/skills/create-spec/SKILL.md · Use when locking down technical contracts for a vertical slice. Creates Spec documents with data models, API surface…
jkaloger/lazyspec · examples/spec/skills/lazy/SKILL.md · Use when starting new work, planning a feature, or deciding what to implement next. Detects existing RFCs, Specs, and…
jkaloger/lazyspec · examples/spec/skills/resolve-context/SKILL.md · Use when an agent needs full context before beginning work on a Spec or Plan. Gathers the document chain from plan…
jkaloger/lazyspec · examples/spec/skills/review-plan/SKILL.md · Use when a Plan is complete and ready for review. Two-stage review -- spec contract compliance first, code quality…
jkaloger/lazyspec · examples/spec/skills/write-rfc/SKILL.md · Use for heavy, cross-cutting, or architecturally significant designs. Creates an RFC document with intent, interface…
jkaloger/lazyspec · skills/advance/SKILL.md · Use when moving a document to its next status along the type's lifecycle DAG, maintaining links across the transition.
jkaloger/lazyspec · skills/co-write/SKILL.md · Use when drafting a document of a configured type collaboratively -- AI proposes a draft body, the human edits, iterate…
jkaloger/lazyspec · skills/configure-type/SKILL.md · Use when adding a new custom document type to a lazyspec project. Interviews the user to co-author the type's…
cursor/plugins · orchestrate/skills/orchestrate/SKILL.md · Use only when the user explicitly types `/orchestrate <goal>` to decompose a large task, spawn a tree of parallel…
rohitg00/pro-workflow · skills/orchestrate/SKILL.md · Wire Commands, Agents, and Skills together for complex features. Use when building features that need research…
hashgraph-online/awesome-codex-plugins · plugins/AgiFlow/ai-plugin/skills/orchestrate/SKILL.md · Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate…
apmantza/pi-lens · .claude/skills/orchestrate/SKILL.md · Load the pi-lens orchestration procedure before briefing, routing, or merging a lane — brief authoring, review intake…
josstei/maestro-orchestrate · plugins/maestro/skills/orchestrate/SKILL.md · Run the full Maestro workflow for complex engineering tasks that need a mandatory design dialogue, approved…
josstei/maestro-orchestrate · antigravity/skills/orchestrate/SKILL.md · Run the full Maestro workflow for complex engineering tasks that need a mandatory design dialogue, approved…
josstei/maestro-orchestrate · claude/skills/orchestrate/SKILL.md · Run the full Maestro workflow for complex engineering tasks that need a mandatory design dialogue, approved…
boshu2/agentops · plugin/skills/orchestrate/SKILL.md · Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead…