Review Workflow

Flow-Next uses review gates before and after implementation.

flowchart LR
  Spec["Spec"] --> PlanReview["Plan review"]
  PlanReview --> Work["Work"]
  Work --> ImplReview["Implementation review"]
  ImplReview -->|needs work| Work
  ImplReview -->|ship| Completion["Completion review"]
  Completion --> PR["make-pr"]

Plan review

/flow-next:plan-review fn-1

Checks whether the spec and plan are complete enough before work begins.

Use it when the work is high risk, cross-module, product-facing, or likely to be delegated. A plan review should catch missing requirements and bad decomposition while the fix is still cheap.

Implementation review

/flow-next:impl-review fn-1

Runs a second model over the diff. Only introduced findings count toward blocking verdicts.

Use a different model or backend than the implementation model when possible. The point is adversarial pressure, not another pass from the same context. The workflow is a loop: review finds introduced issues, /flow-next:work fixes them, review runs again, and the handoff continues only once the verdict is shippable.

Completion review

/flow-next:spec-completion-review fn-1

Checks the combined implementation against the whole spec after all tasks are done.

This is different from implementation review. Implementation review checks a diff. Completion review checks whether the full spec is satisfied after all tasks, merges, and fix loops.

PR review

/flow-next:make-pr fn-1
/flow-next:resolve-pr 123

The PR body summarizes acceptance coverage, critical files, decisions, memory, deferred findings, and review focus.

Review escalation

Signal	Response
Plan review finds unclear product behavior	Rerun /flow-next:interview --scope=business
Plan review finds technical gaps	Rerun /flow-next:interview --scope=technical
Impl review finds introduced bug	Rerun /flow-next:work on affected task
Impl review flags architectural mismatch	Revisit spec decision context
Completion review finds uncovered acceptance criteria	Add or repair task coverage
Human reviewer is confused	Improve task summaries or regenerate PR body

Review is part of the workflow, not an afterthought at the end.