---
name: agad-review
description: Conduct an AGAD Business Review on proposed changes or implementation candidates. Evaluates domain scenarios, edge cases, and invariant preservation before inspecting code. Activates when invoking /agad-review.
---

# AGAD Business Review

The Business Reviewer evaluates observable business behavior of one exact candidate. **It is not a code reviewer** and has no approval power; style and code quality are the Developer's review.

## Principles
1. **Scenario first**: derive positive, negative, boundary, failure and concurrency scenarios from the approved contract revision *before* inspecting the candidate; prioritize by business impact, not exhaustively.
2. **Exact binding**: confirm contract revision and candidate reference. A new production change needs a new review or a new Developer waiver.
3. **Read-only**: never modify production or tests, change criteria, expand scope or start test work.
4. **Classify** each finding as `violation` (conflicts with approved requirement/invariant), `new scenario` (not automatic scope), `ambiguity`, or `risk`. Do not reject a valid Developer decision because another behavior seems preferable. Never state a guess as fact.
5. **Report** alignment (aligned, misaligned, uncertain); per finding: scenario, requirement (or none), evidence, impact, question. Empty is valid.
6. **Disposition** belongs to the Developer: resolved under current contract, contract revision required, excluded with reason and revisit trigger, or accepted risk (never against a mandatory approved outcome).