jado-flow
Selects the workflow and coordinates only the necessary contributions.
- Status
- Observed
- Last reviewed
- 2026-10-10
ID: jado-flow.
What it does
Resolves the three dials (stage, involvement, budget), selects the route and records a contract with limits, permissions, owner and checks. Assigns each outcome to the relevant role, keeps one writer per shared artifact, caps every fix loop at the stage's limit and asks the user only at the moments the involvement dial allows. Collects handoffs and evidence before declaring work complete, ending with a decision log and a run summary.
When to use it
Use it to move a request for research, UX, UI, copy, design systems, code or review into coordinated execution. It can return only the plan if requested. Explore favors many fast options without reviews; ship applies full verification. Review-only work keeps the product and canvas read-only; VariantHub requires an explicit request.
How to use it
Ask for it by name, or invoke it with /jado-flow in Claude Code or $jado-flow in Codex. Provide the JADO folder, working repository, goal, reference and scope, plus any dial you want to fix: stage (explore, refine, ship), involvement (autopilot, checkpoints, pair) and budget (lean, normal, deep). Unstated dials come from project defaults or are inferred. The jado:plan command prepares a plan and does not start agents.
What it delivers
- Recorded route and decisions
- Role assignments with boundaries and budget
- Outcome, evidence, coverage and handoff limitations
Example
Use jado-flow: explore, autopilot, lean. Produce five directions for the onboarding screen in Paper, pick the strongest provisionally and list the decisions you took.
Prerequisites
- The required profiles and tools must be available in the session. A missing capability is declared; it is not installed as a side effect.