Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.
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
# Subagents Orchestration Guide
## Role: The Orchestrator
**Explicit User Instruction**: The user explicitly instructs and authorizes every subagent call named in the invoked recipe. Execute each applicable call when its prerequisites are met.
The orchestrator owns workflow decisions, routing, progress management, user interaction, the investigation and validation needed for those decisions, and explicitly assigned mechanical operations, using any available tool. Named specialists own explicitly assigned investigation and semantic deliverable creation or modification; invoke them before producing or changing code, tests, configuration, documents, task files, or other artifacts.
### Workflow Subagent Context — Mandatory
…
The line at the top of this page pins the label git:20261029.29a1f7c, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_6q4ho2mudhm2jqme
GET https://markdownregistry.com/api/v1/resolve?ref=shinpr/claude-code-workflows/subagents-orchestration-guide
GET https://markdownregistry.com/api/v1/blob/954c427496be6376b2325f0e14595e0258ea10c58b28172a2142b31d5f02c9db
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.
shinpr/claude-code-workflows · dev-skills/skills/coding-principles/SKILL.md · Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features…
shinpr/claude-code-workflows · dev-skills/skills/documentation-criteria/SKILL.md · Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when…
shinpr/claude-code-workflows · dev-skills/skills/external-resource-context/SKILL.md · Records where resources outside the repository live (design source, design system, API schema, IaC source, secret…
shinpr/claude-code-workflows · dev-skills/skills/integration-e2e-testing/SKILL.md · Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when…
shinpr/claude-code-workflows · dev-skills/skills/requirement-convergence/SKILL.md · Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded…
shinpr/claude-code-workflows · dev-skills/skills/testing-principles/SKILL.md · Language-agnostic testing principles for choosing which tests a change needs, test quality, and proof ownership, with…
shinpr/claude-code-workflows · dev-skills/skills/typescript-rules/SKILL.md · React/TypeScript frontend development rules including type safety, component design, state management, and error…
