Product
Give each decision the right tool.
Start with Flow to organize the project. Use the supporting tools when you need to clarify the brief, direct an agent, or review the evidence.
Organize the project
Give the work a home and define the conditions for moving forward.
Plan and direct the work
Make the requirements, instructions, and authority clear before an agent acts.
Requirements
Agree on what the agent should build.
Turn product decisions into acceptance criteria, then compare the supplied implementation references with those decisions.
Instructions
Give the next agent the instructions that apply.
Resolve repository rules, scope, and precedence into a focused instruction pack with its sources attached.
Rules
Review an agent action before it exceeds the brief.
Compare proposed actions with an explicit authority contract covering paths, commands, hosts, and budget.
Models
Compare models on work you would accept.
Bring candidate run evidence and compare accepted outcomes, cost, and task constraints using the same evaluation criteria.
Keep work moving
Preserve context when a task changes hands or a dependency gets in the way.
Handoffs
Continue the work without reconstructing the conversation.
Package the objective, repository state, decisions, evidence, and blockers so another agent can see where to continue.
Blockers
Find useful work while something else is stuck.
Map dependencies, owners, and work status to see what can proceed and what must be resolved first.
Review what the evidence supports
Use the right observations to evaluate the claim, state, boundary, or transition.
Checks
See what the evidence supports before you ship.
Compare software claims with observed checks and review what is verified, blocked, failed, or still untested.
Coverage
See which product states still need a test.
Define roles, devices, data states, and constraints, then compare supplied observations with the resulting state map.
Access
Find where observed permissions disagree with the rules.
Compare expected access with observations across roles, tenants, and actions to identify permission mismatches.
Migrations
Review the evidence before a database change.
Evaluate migration scenarios, constraints, observations, and recovery evidence before deciding whether a change is ready.