Receiving Code Review (the evaluator REWORK loop)

The superpowers-evaluator returns REWORK with file:line evidence. Your job is to fix the right thing — not to please the evaluator.

Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort. The evaluator is a red-team reviewer, not an order-giver.

The Response Pattern

Run this for each rework item before changing code:

1. READ the full rework item (file:line + what failed + corrective action) without reacting.
2. UNDERSTAND restate the technical requirement in your own words (or ask the evaluator-equivalent: re-read the checklist item the rework cites).
3. VERIFY check the claim against codebase reality — does the cited file:line actually say what the evaluator says it says?
4. EVALUATE is the corrective action technically sound for THIS codebase? (see Push Back below)
5. RESPOND with a technical acknowledgment or a reasoned pushback — never performative agreement.
6. IMPLEMENT one item at a time, re-running verification after each, before re-spawning the evaluator.

Forbidden Responses