Build your own workflow

User workflows live in ~/.slo/user_workflows/ and sit alongside the built-in Feature Specifications and Code-Test-Review workflows. The easiest way to create one is to ask Slo to do it for you.

Ask Slo to build the workflow

Describe what your workflow should do in plain language:

"Create a user workflow for our deployment process — it should check for open PRs, run the test suite, tag the release, and post to Slack."

"Build me a workflow that takes a raw bug report and produces a triage document with a severity rating, affected files, and a suggested fix."

"I want a workflow that reviews all open GitHub issues every Monday morning and produces a priority-ordered list for the team standup."

Slo uses its built-in create-user-workflow skill to scaffold the workflow, define the steps, and save it to ~/.slo/user_workflows/<your-workflow-name>/.

What Slo creates

~/.slo/user_workflows/
  your-workflow-name/
    WORKFLOW.md       ← orchestration steps
    phases/           ← one file per phase (optional)

Running your workflow

Once created, trigger it like any built-in workflow — just describe the goal:

"Run the deployment workflow for the staging environment."

"Run the Monday triage workflow."

Slo recognises the intent and runs your workflow's phases in order.

Composing skills inside a workflow

Workflows can reference skills by name or describe what each phase should do. Slo loads the relevant skills automatically for each step.

If a phase needs a specific skill, mention it in your workflow description:

"The second phase should use the code-review skill with a thorough audit."

Editing a workflow later

Workflow files are plain markdown. Open ~/.slo/user_workflows/<workflow-name>/WORKFLOW.md and update the steps directly. You can also ask Slo to revise it:

"Update the deployment workflow to also create a GitHub release after tagging."