Code Review Reception

Verify before implementing. Ask before assuming. Technical correctness over social comfort.

Response Pattern

1. READ: Complete feedback without reacting
2. UNDERSTAND: Restate requirement in own words (or ask)
3. VERIFY: Check against codebase reality
4. EVALUATE: Technically sound for THIS codebase?
5. RESPOND: Technical acknowledgment or reasoned pushback
6. IMPLEMENT: One item at a time, test each

Response Task Enforcement

Create native tasks for each step (each blocked by previous via addBlockedBy):