Orchestra Engine

Orchestra is an OpenClaw plugin that powers the /orch slash command. It loads Markdown blueprints, lets the LLM/agent pick the right blueprint for a user brief, and hands the full workflow off to an isolated agent session.

What you can do with /orch

At a high level, blueprints can support scenarios like:

• Content creation (for example: /orch Create a blog post about plant based protein)
• Research flows (for example: /orch Research the latest trends in electric vehicles)
• Other multi-step workflows that are encoded as blueprints (tweets, reports, summaries, etc.)

The exact workflows available depend on the blueprints present in your configured repositories and how they are described in their blueprint-index.md files.

Prerequisites

• OpenClaw gateway >= 0.7 with slash commands and skills enabled.
• Orchestra plugin installed on the gateway, your OpenClaw admin should run openclaw plugins install @gekkocompany/orchestra.
• Blueprint repositories Use the command /orch blueprints init [project?] gitRepo [gitPAT?] to install your blueprint repository on the gateway correctly, for example: Orchestra/repos/acme-content-blueprints containing blueprint-index.md and ./blueprints/*.md blueprints.

Using /orch

status

/orch status

Checks orchestra status

run

/orch [project?] <brief>

Finds and starts the blueprint to create your artifact

abort

/orch abort

Stops the currently running blueprint.

blueprints init

/orch blueprints init [project?] <gitRepo> [gitPAT?]

Initializes a blueprint project by cloning its repository into the Orchestra workspace.

blueprints add

/orch blueprints [project?] add <brief>

Guides you through creating and saving a new blueprint in the selected project.

blueprints update

/orch blueprints [project?] update <blueprint name>

Requests an update to an existing blueprint; -- currently this command is not yet implemented.

blueprints refresh

/orch blueprints [project?] refresh

Refreshes a project’s blueprints so they are up to date with their remote repository.