October 1, 2026
Kiro development follows a recipe: Workflows connect implementation, review and fixes
Kiro runs a saved development recipe: executes steps in order, distributes work in parallel and retries.
Kiro
@kirodotdev
Introducing Kiro Workflows: now generally available. 👻 Orchestrate complex agent work beyond prompts and sessions. Run work sequentially. Distribute it in parallel. Repeat steps based on results. Choose agents, models and reasoning effort for each step. All of this is defined in the workflow itself. Refine it. Save it as a recipe. Run it again. Detailed walkthrough: http://spr.ly/6010BGtGea
· 520 views
In Kiro's Sep 30 feature-pipeline recipe, the implementation loop allows 3 attempts to secure review approval.
Previously, developers manually triggered implementation, review and fixes. Now they describe that sequence in a workflow, and Kiro executes it on its own. A workflow here is a recipe for AI agents that can be saved and reused for another task.
The recipe controls the steps. Each step gets a separate session with fresh context. You can choose its agent, model and reasoning effort. In the published feature-pipeline, the architecture is also reviewed up to 3 times, while claude-opus-5.5 and gpt-5.6-sol review the code in parallel with Extra high effort.
You can create a recipe in the main chat by describing the result you want. Kiro offers 3 ready-made options:
- `investigate` for investigating a task. - `feature-pipeline` for development. - `publish-pr` for creating a PR and handling reviews.
Setup depends on the app. According to the Sep 30 changelogs, Workflows are enabled as follows:
- In Kiro IDE 1.2.4, open Workspace Configuration → Workflows or enable `kiroAgent.workflows.enabled` in Settings. Then start a new chat. - In Kiro CLI 2.26.0, open `/settings` → Features in a V3 session, enable Workflows and restart the CLI. - In Kiro Web, open Settings → Workflows → Enable workflows.
Project recipes are saved in `.kiro/workflows/`, and personal recipes in `~/.kiro/workflows/`. The documentation includes a 2-step example with a ready-to-use command:
```text /workflow run plan-and-implement --task "Describe the change" ```
In Kiro Web, you can upload a recipe through Upload workflow in `.workflow.json`, `.workflow.yaml` or `.workflow.yml` format. Configuration Sync imports the `.kiro/workflows/` folder.
Workflows consume standard Kiro credits. Pricing as of Sep 30, 2026:
| Plan | Monthly price | Monthly credits | | --- | --- | --- | | Pro | $20 | 1,000 | | Pro+ | $40 | 2,000 | | Pro Max | $100 | 5,000 | | Power | $200 | 10,000 |
An additional credit costs $0.04.
The Kiro team used workflows to build most of the recipe execution engine and the entire Kiro Web integration. According to engineers Romain Dura and Doug Clauson on Sep 30, a typical run contains 5–10 steps, and the team has completed thousands of runs. They used separate Git worktrees for parallel implementations: Workflows do not create them or isolate Git branches automatically.
The Kiro team already uses saved recipes to develop the tool itself.
