Builder Review Loop

Use a two-agent workflow:

• The builder agent implements the requested slice.
• The reviewer agent reads the real files, not just the summary, and helps the user decide whether to fix, defer, revert, or proceed.
• The human owns scope and final decisions.

Core Rules

• Treat the builder summary as a claim, not proof. Read the touched files.
• Findings come first. Prioritize bugs, regressions, scope drift, and contract breaks over style.
• Separate must fix now from can defer.
• Keep prompts narrow: one bug fix or one feature slice at a time.
• Do not silently reopen product or architecture decisions that the user already made.
• Prefer a fresh conversation when context is bloated and the next agent can reconstruct state from the code.

Review Workflow

1. Read the builder summary and exact files changed.