Skip to Content
kusaw docsv1.0.0

Custom steps

A [step](../glossary.md#step) is a program. Kusaw sends it a request, it reports progress, and it ends with a result. Every step, built-in or [custom](../glossary.md#custom-command-step), speaks the same [step protocol](../glossary.md#step-protocol). The [built-in steps](../glossary.md#built-in-step) are defaults you can replace.

A step is a program. Kusaw sends it a request, it reports progress, and it ends with a result. Every step, built-in or custom, speaks the same step protocol. The built-in steps are defaults you can replace.

When to write a step

Write a custom step when you have something of your own to run:

  • a check you already run
  • a tool you trust
  • your own agent prompt
  • a different review

A config change is enough when you only need to adjust a default: its timeout, retries, fail_on, verification commands, or which MCP servers and skills it may use. You do not need a custom step to rename a timeout.

Built-in steps are defaults

builtin: <name> and command: [...] start the same way. Kusaw handshakes the program, sends the request, and reads progress and a result. Replacing the default review step, or the default build step, does not change gates, loops, or feedback as long as you keep the same step id.

In this section

On this page