jiruidai/dsh-meta-orchestrator

Install

All of this behavior comes from one short instruction block the plugin adds to the agent's system prompt — no extra model calls, no background processes.

### What gets installed

| Added to your agent | What it is |
|---|---|
| An instruction block (~330 words) | Teaches the plan-first protocol above; sits in the system prompt of every session |
| Five pattern playbooks | Skills in the catalog; cost nothing until the model loads one |
| `orchestrate` / `adapt_workflow` / `complete_workflow` | The three recording tools: save the plan, revise it, close it |

## 🧩 Why it's built this way

- **The model is the planner** — no hard-coded pipeline and no fixed agent topology decides how your task runs; the model picks and composes per request, and may deviate when the task demands it.
- **Recording, not executing** — the plugin holds no runtime, no scheduler, no message bus. Execution stays on the harness's battle-tested primitives, so there is nothing extra to break.
- **Plans survive restarts** — every plan lives in DSH's storage domain as an append-only `create → adapt* → complete` chain, fenced per session lifecycle. No custom session event types, so orchestrated sessions always resume cleanly.
- **Built to track a fast-moving harness** — only stable public plugin surfaces are used; nothing is pinned to harness internals.

Add jiruidai/dsh-meta-orchestrator to your DSH config (web profile) to enable.