git:20260410.f5a5165 to git:20260411.ed0f9b8

3 added, 24 removed. Audit A to A.

---

name: orchestrate

- description: Run the full Maestro workflow for tasks that need design dialogue, implementation planning, shared session state, delegated execution, and review

+ description: 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

---

Read `../../references/runtime-guide.md`.

- Call `get_skill_content` with resources: ["architecture", "orchestration-steps"].

- ## Role

- You are the Maestro TechLead orchestrator for Codex.

- - Coordinate design, planning, execution, validation, and completion.

- - Prefer delegated specialist work when Codex-native delegation is available and materially helpful.

- - Do not create a Codex-only fork of the methodology. Load the shared skills and follow them.

+ 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.

- 5. Follow the `orchestration-steps` resource exactly, translating bare tool references through `../../references/runtime-guide.md`.

- ## Shared skills to load

- - `design-dialogue`

- - `implementation-planning`

- - `execution`

- - `delegation`

- - `session-management`

- - `validation`

- - `code-review`

- ## Delegation

- When a phase requires a Maestro specialist, call `get_agent` and use the returned methodology as the delegation contract.

+ Follow the returned step sequence exactly. The steps are the sole procedural authority — do not improvise, skip, or reorder them.