Documentation

Flow

The steps Vibestrate works through to finish your task - plan, build, check, fix.

A Flow is the list of steps Vibestrate works through to finish your task.

Think about hiring someone to remodel a kitchen. A good one doesn’t just start swinging a hammer. They draw up a plan, do the work, walk through to check it, and fix anything that’s off before they call it done. A Flow is that routine, written down, so every task gets the same care instead of depending on luck.

When you run a task without choosing a Flow, Vibestrate uses the one it ships with:

vibe run "Refactor provider permissions"

That default Flow goes Plan, then Build, then Check, then Fix:

PlanWork out what to change before touching anything.

BuildWrite the code.

CheckRun your tests, then review the change.

FixIf the check finds problems, loop back, fix, and check again.

For most work, that is all you need.

Picking a sturdier Flow

Some changes deserve more care. A change to login or payments might want a second reviewer to read the result with fresh eyes before it is blessed. For those, ask for a heavier Flow:

vibe run "Tighten the auth checks" --flow quality-arbitration

Vibestrate ships a handful of built-in Flows. You can install more from the shared hub, or write your own. Browse the built-in Flows →

Why a Flow never names your AI

This is the part that makes a Flow shareable. A Flow describes the steps, and the kind of worker each step needs - “this one needs a builder”, “this one needs a reviewer”. It never says which AI model does the work.

The routine is shared, the workers are yours. A Flow names the steps and the kind of worker each one needs, never the model. That is why you can lift someone else’s Flow off the hub and run it with your own models and budget.

Your Crew decides that. So you can take a Flow someone else wrote, off the hub, and run it with your own models and your own budget. The routine is shared; the workers are yours.

When it’s worth writing your own

Reach for a custom Flow when:

A routine keeps repeating The same review steps show up across your tasks, so you bottle them once.

A change needs a gate A certain kind of change should always pause for your approval at a set point.

A step is pinned to a model You want one step to always run on a specific model, like the reviewer on a different vendor.

If you only want to nudge the default a little, a clearer task description or a skill usually does the job with less effort.

Going deeper

Built-in Flows reference - every shipped Flow, step by step, plus parallel review panels and parameters.
Add a Flow - write, validate, and share your own.
Seat and Crew - who fills a Flow’s steps, and what they cost.