Before implementing behavior-changing work, write a review checklist to .agents/reviews/<DD>-<MM>-<YYYY>-<short-description>.md and wait for the user to check every box. Implementation starts ONLY after all items are [x].
Write a review checklist when all of these hold:
- Behavior-changing, not mechanical β new tables, new cron/scheduled jobs, new agent prompts/decision rules, or changes to how the system acts in production (vs. a rename, a UI tweak, an obvious bugfix).
- There are real design decisions the user could disagree with β metric semantics, schema shape, where logic lives, prompt policy.
- Multi-part enough that "ok" in chat is ambiguous β the checklist forces item-by-item agreement instead of interpreting a general approval as full-scope approval (see Gotcha #3).