Core
Flow
Organize a GitHub project into phases with explicit acceptance criteria. Review the evidence behind each gate and see what needs attention before the next phase.
Last updated August 22, 2026
Move the project forward when the work is ready.
Use cases
Agree on what ready means
Define the criteria for each phase so the team and its agents work toward the same outcome.
Review the basis for progress
A criterion derives its status from attached evidence. An unverified claim stays visible instead of counting as a pass.
Keep the project instructions close
Pin the documents and design instructions an agent should read before changing the project.
How it works
- 1
Connect the project
Choose a GitHub repository and open its project workspace.
- 2
Set the phase requirements
Review the phase criteria and pin the context needed for the work.
- 3
Review before advancing
Inspect the gate result, resolve missing evidence, and decide what should happen next.
Quickstart
Open Flow in the console, provide the required inputs, and start an organization scoped run.
Inputs
- project and phase template
- criteria with attached evidence
- pinned context documents
- DESIGN.md sections and design dependencies
Outputs
- advance, hold or blocked verdict
- derived criterion status
- computed phase health
- DESIGN.md and DESIGN-DEPENDENCIES.md
MCP
Call Flow from a compatible agent with the preferred public tool name.
The previous internal service identifier remains accepted for compatibility, but new integrations should use this product name.