enterprise-review

name	enterprise-review
description	Use when enterprise implementation is complete enough for a structured review that separates spec compliance from code quality and classifies drift explicitly

Enterprise Review

Review the work in two stages. Never mix them.

Required Background

• code-reviewer
• requesting-code-review

Stage Order

Use review-separation.md.

1. Stage 1: spec compliance
2. Stage 2: code quality

If Stage 1 fails, Stage 2 does not start.

Before review starts, run the agent-bound review gate in agent-stage-gates.md.

For non-trivial, schema-sensitive, tenant-sensitive, money/order/inventory/invoice, or UI workflow changes, review should be multi-agent when available: split spec/contract, schema/data, code execution, E2E/workflow, security/tenant, and headless UI lenses. If delegation is unavailable, run the same lenses sequentially and label the limitation.

Required Checks

• every contract item has a matching implementation target
• every contract item has a real test
• changed files are classified as required, enabling, or drift
• proof scope in the contract still matches the implementation reality
• contract traceability statuses are updated from pending to their real state before handoff
• schema/query claims have current-code reads plus real DB proof, not migrations/diffs/mocks
• every changed runtime file has code-level execution proof
• every cross-layer behavior has source-to-consumer E2E trace and edge-case coverage
• UI/PDF/file/upload/rendered workflows have headless browser proof
• repo gate matrix commands are present and credible: PR body/delivery gate, no-new-mock guard, DB ownership gate, live-proof registry, and required CI mirrors
• the review is against the current final diff. If CI or a gate forced a code pivot, earlier review output for affected files is stale and must be rerun.

Reviewer Independence

If an independent reviewer is available for medium or large work, use one. If not, perform the review yourself but label the limitation explicitly. Do not pretend self-review is the same as independent review.

If the prompt explicitly states that the committed repo profile and repo-local overlay are already current, review should proceed without reopening discover work unless the diff reveals profile drift.

When the review artifact is written, record it in the current agent session before moving to forge or verify.

Completion Handoff

• Writing the review artifact is not the finish line.
• If the current prompt asks for completion, verification, or an end-to-end cycle, review must hand off directly to enterprise-verify in the same lane.
• Do not stop after review waiting for another prompt unless the user explicitly asked for review-only output.