Maestro-orchestrate orchestrate

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

install

source · Clone the upstream repo

git clone https://github.com/josstei/maestro-orchestrate

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/josstei/maestro-orchestrate "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/maestro/skills/orchestrate" ~/.claude/skills/josstei-maestro-orchestrate-orchestrate-84afab && rm -rf "$T"

manifest: plugins/maestro/skills/orchestrate/SKILL.md

source content

Read

../../references/runtime-guide.md

. Call

get_skill_content

with resources: ["orchestration-steps"].

Startup

If
```
get_runtime_context
```
appears in your available tools, call it first.
Prefer Maestro MCP tools for settings, workspace initialization, session status, planning validation, and session transitions.
If MCP tools are unavailable, use direct file operations under
```
docs/maestro
```
.
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.