Built-in Flows
Every Flow that ships with Vibestrate, with its seats and its ordered steps.
Built-in run Flows. Project Flows live in `.vibestrate/flows/<id>/flow.yml` and follow the same schema (src/flows/schemas/flow-schema.ts).
--flow default
Plan → implement → validate → review. Changes requested go straight back to the implementer - who self-reviews its own diff before every hand-off - until the reviewer approves or the loop budget runs out. The reviewer judges the whole execution against the plan and project rules, and can run the tests itself.
--flow deep
The heavyweight pipeline: plan → architect → implement → validate → review, with a dedicated fixer answering review rounds and an independent verify gate deciding merge-readiness.
--flow plan-only
Plan + review only - WRITES NO CODE. A planner turns the task into a concrete plan and a reviewer critiques it; nothing is implemented, validated, or written to disk. Produces a vetted plan and an APPROVED / BLOCKED verdict. Do not pick this for tasks that need code changes - it is for thinking a change through before building it.
--flow quality-arbitration
Cross-provider planning, review, implementation, challenge, second review, and Vibestrate decision summary.
--flow pickup
Execute a card item-by-item: a holistic plan once, then micro-plan → implement repeated per checklist item in one worktree (compact summaries carried forward, a commit per item), then a holistic review.
--flow panel-review
Plan, architect, implement, and validate, then fan out a 3-lens read-only review panel (correctness, tests, security/risk) over the real diff and an arbiter join that renders one verdict. Heavier - selected only when evidence warrants it.
--flow pickup-analysis
Execute a card item-by-item with a per-item analysis fan-out: a holistic plan once, then for each checklist item two read-only analysts (risk/impact + tests) run in parallel and the implementer writes the item informed by both (a commit per item), then a holistic review.
--flow pickup-review
Execute a card item-by-item with a per-item REVIEW panel: a holistic plan once, then for each checklist item the implementer writes it and a per-item panel (correctness + risk) plus an arbiter review THAT item's diff; a per-item fix loop runs before the item commits, then a holistic review.
--flow saga
Sequence a multi-step saga item-by-item with a LIGHT per-item review: a holistic plan once, then for each step the implementer writes it and a SINGLE reviewer checks that step's diff for bugs and security/risk and renders APPROVED / CHANGES_REQUESTED; a per-item fix loop runs before the step commits, then a holistic review. Lighter than pick-up (per-item review) - one reviewer, no arbiter panel.
--flow security-review
Plan, architect, implement, and validate, then fan out a 3-lens read-only SECURITY panel (authorization, secrets/exposure, injection & unsafe input) over the real diff and an arbiter join that renders one verdict. The flow the `security` supervisor persona prefers.
--flow express
One implementer turn for small, low-risk tasks. Validation is scoped to the actual change, and review plus verification run only when the diff demands it - any non-prose or protected file gets both a real review turn and a real verify turn.
--flow scaffold
A small parameterized example: scaffold a starter project from a name + framework. Shows how a flow declares `params:` and substitutes them into step instructions with {{params.x}}.
--flow research
Answer a question in writing, with sources, checked by a second seat for whether the claims are actually supported. Produces a document, not a diff - nothing is written to your repository.
--flow spec-up-intake
Spec-up phase link 1 - WRITES NO CODE. The CTO reads the brief and asks the gap questions needed to scope the work (auth? payments? scale? persistence?). Emits a structured questions artifact; the answers seed the spec-up run. Launched by 'Plan'.
--flow spec-up
Spec-up phase link 2 - WRITES NO CODE. The CTO turns the brief + answers into a scope, a spec, an architecture with a provisioning checklist, and a risks register, then a reviewer checks completeness against the approved scope. Produces reviewable spec/architecture/risks drafts. Launched after the intake questions are answered.
--flow spec-up-roadmap
Spec-up phase link 3 - WRITES NO CODE. Resumes the approved spec and synthesizes the spec/architecture/risks into an ordered, dependency-aware roadmap proposal (board cards with acceptance criteria and estimates). Review and accept it from the proposals surface. Launched after the spec is approved.
