Skip to content

Review Gates

  • Goal is clear.
  • Context files are ordered.
  • Constraints and non-goals are explicit.
  • Expected outputs are named.
  • Verification requirements exist.
  • Adapter supports required capabilities.
  • Sandbox backend is available.
  • Required skills can be loaded or approximated.
  • Output satisfies linked issue/spec/mission criteria.
  • Any deviations are documented.
  • Changes are coherent, minimal, and maintainable.
  • Docs are navigable and understandable.
  • Code, when present, follows project conventions.
  • No unexpected writes outside sandbox.
  • No secrets stored in artifacts.
  • Risky commands/actions are documented.
  • Human reviewer approves selected changes for canonical state.
  • Promotion record is written.