Run the full Maestro workflow for complex engineering tasks that need a mandatory design dialogue, approved implementation plan, and then execution with shared session state.
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
Read `../../references/runtime-guide.md`.
Call `get_skill_content` with resources: ["orchestration-steps"].
## Startup
1. If `get_runtime_context` appears in your available tools, call it first.
2. Prefer Maestro MCP tools for settings, workspace initialization, session status, planning validation, and session transitions.
3. If MCP tools are unavailable, use direct file operations under `docs/maestro`.
4. Treat `docs/maestro` as the workspace state root.
Follow the returned step sequence exactly. The steps are the sole procedural authority — do not improvise, skip, or reorder them.
The line at the top of this page pins the label git:20260411.ed0f9b8, 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_g2x5dr3dqdyp2vwd
GET https://markdownregistry.com/api/v1/resolve?ref=josstei/maestro-orchestrate/orchestrate
GET https://markdownregistry.com/api/v1/blob/84afab5e080115d17317dfcfb99d7c873ff70de4b558932a4afe18a436aaddfd
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.
josstei/maestro-orchestrate · claude/skills/a11y-audit/SKILL.md · Run a Maestro-style accessibility audit for WCAG compliance, ARIA usage, keyboard navigation, and screen reader…
josstei/maestro-orchestrate · claude/skills/compliance-check/SKILL.md · Run a Maestro-style regulatory compliance review for GDPR/CCPA, cookie consent, data handling, and licensing
josstei/maestro-orchestrate · claude/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/perf-check/SKILL.md · Run a Maestro-style performance assessment for hotspots, regressions, and optimization planning
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…
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…
boshu2/agentops · skills/orchestrate/SKILL.md · Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead…
aperivue/medsci-skills · skills/orchestrate/SKILL.md · Use when the user describes a research goal without naming a skill, or the task spans several skills. Classifies the…
