Workflows overview
A workflow is a fixed process with checkpoints. Where a skill teaches Slo how to do one thing, a workflow strings several together and won't move on until each step passes. Slo ships with two, and they're designed to be used one after the other.
| Workflow | Takes | Produces |
|---|---|---|
| Feature specifications | A rough request or ticket | A checked spec, split into tasks |
| Code-test-review | A spec or one task from it | Tested, reviewed code, checked against the spec |
Starting one
Describe the goal. Slo recognises the intent:
"Write a feature specification for partial refunds."
"Implement task 12.b from specifications/12-refunds/."
Naming the workflow removes any doubt: "use the code-test-review workflow".
Step by step, or straight through
By default, Slo stops at the end of each step, tells you what it finished and what comes next, and waits. Reply with "continue", a correction ("revise the review before moving on"), or "stop here".
If you'd rather not be asked, say so up front:
"Run the code-test-review workflow for task 12.b to completion."
Running a workflow with sub-agents
Add "use dynamic workflows" and each step goes to its own sub-agent with a clean context, supervised by an orchestrator. Add "detached" or "in the background" and it runs without tying up your session.
"Use dynamic workflows to run code-test-review for task 12.b, detached."
See Dynamic workflows and Supervise a dynamic workflow.
Your own workflows
You can write workflows for your team's own processes, such as a release checklist or a bug triage. See Build your own workflow.