Post-Implementation Review Gate

Use an independent reviewer to catch defects that the implementing context is likely to overlook. The reviewer supplies a second perspective; the primary agent remains responsible for evidence, fixes, verification, and the final answer.

Gate outcome

Do not declare a review-triggering implementation complete until one of these outcomes is true:

• an independent review completed and every finding was verified and dispositioned;
• independent review was unavailable because delegation was forbidden or remained unavailable after one bounded retry, and the final answer identifies the local fallback performed.

The gate does not broaden authorization. Keep production changes, external writes, destructive actions, secrets, and unrelated work outside the scope originally granted by the user.

Delegation permission preflight

Before declaring delegation forbidden, read the complete active orchestration rule, including every exception. A rule such as “do not spawn subagents unless the user, an applicable AGENTS.md, or an applicable skill explicitly asks” permits the one isolated, read-only reviewer required by this skill: step 5 below is the applicable skill's explicit request.

This permission is narrow. It authorizes only the independent reviewer needed for this gate and does not authorize implementation delegation, extra reviewers, writes, external side effects, or broader scope. An unconditional higher-priority prohibition still wins.