Skip to main content
This guide walks through building a minimal orchestration: one goal, two allowed workflows, and a slash command that opens an instance on demand. It takes about ten minutes.
You don’t have to build everything by hand. Open Assistant in the sidebar and ask it to draft the workflows or the orchestration for you, or to guide you through any step in this guide.

​
Before you start

You need at least one published workflow in the project. An orchestration routes between existing workflows; it does not replace them. If you have none yet, start with Workflows. If your workspace already maintains an orchestration template in the Workspace Library, you can skip the build and select Install from Library on the Orchestrations page instead.

​
Create and configure

1

Create the orchestration

Open your project and go to Build > Orchestrations, then select New Orchestration. Overcut creates a draft and opens the Builder. The draft stays private until you publish it.
2

Name it and write the goal

With nothing selected on the canvas, the right panel shows the orchestration settings. Set the Orchestration name. Then select the Goal & Instructions node and write the Goal: the outcome that means the item is done, for example “Every production bug reported as an issue is investigated, root-caused, fixed behind a PR, and verified.” The goal must be at least 20 characters.
3

Select the allowed workflows

Select the Allowed Workflows node and pick the workflows instances may route between. Start small: a triage workflow and an implementation workflow are enough. The AI can only propose workflows from this list.
4

Add an entry trigger

In the Triggers container, select Add Trigger. For Entry event, choose slash command and enter a command such as investigate (without the leading slash; it is saved lowercase). Then set Starts with workflow to the workflow that should always run first. The first workflow is deterministic: no AI decision happens at entry.
5

Add a gate (optional)

Select Add Gate to require human approval before a sensitive workflow runs, or before the instance is marked complete. You can skip this for a first test and add gates later. See Orchestration Builder for gate options.
6

Publish

Select Publish in the top bar. If anything is invalid, the Builder highlights the sections to fix. In the Publish Changes dialog, write a short Publish Message and confirm. New instances start from this published version.
7

Activate

After the first publish, use the activation toggle in the top bar to turn the orchestration on. Inactive orchestrations ignore their triggers.

​
Run it

Comment /investigate (your slash command) on an issue or pull request in a connected repository. The trigger opens an instance and starts the first workflow. Follow the run in the orchestration’s Activity tab: the instance appears in the live funnel, and View Details opens its decision trail. See Monitoring Instances.
If the same slash command is also used by a workflow, the orchestration entry takes precedence. The publish dialog warns you about collisions.

​
Where to go next