Build repeatable workflows

A blueprint defines the process a run follows. Use one when a task needs repeatable steps, such as preparing a repository, implementing a change, running checks, and publishing a result.

Choose an existing blueprint

Open Blueprints and select the project you intend to use. Review the steps and required inputs. System blueprints provide maintained workflows; organization blueprints let your team define its own process.

Requirements are checked for the selected project. A missing connection, secret, input, or capability binding can make an otherwise valid blueprint unavailable.

Define the steps

Use shell commands for work with an explicit command and agent steps for work that needs reasoning or editing. Supported integration and capability-pack steps connect the workflow to the external operation they define.

Prefer commands already maintained in the repository, such as its package-manager scripts. Give agent steps a concrete result and a way to check it. Do not include secrets in the instructions.

Understand versions

Runs use a fixed blueprint version and capture the step contracts and inputs needed for that execution. Editing the workflow for later work does not change an existing run.

Read the selected version before using it on a sensitive repository. A familiar blueprint name is not a substitute for checking its current steps and required access.

Provide inputs

Some inputs are supplied when starting a run; others come from configured organization values or secrets. Fill the required fields and resolve readiness errors before submitting.

A capability pack supplies a supported integration operation or agent tool. Its version and binding determine what the step can do. Check the connected system, required inputs, and intended output rather than granting broad access to solve a setup error.

Test a new workflow

Start with a small task on an appropriate repository. Inspect each step's result and the final outcome. Confirm that failures are visible and that publication occurs only where the workflow intends it to.

For programmatic input and result handling, see the agent reference.