---
name: receiving-code-review
description: Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification, not blind implementation.
graph:
  domains: [domain:software-engineering]
  skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop]
  workflows: [workflow:feature-development]
  topics: [topic:developer-experience]
  roles: [role:tech-lead, role:backend-engineer]
2. UNDERSTAND - Restate requirement in own words
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

## When to Push Back

- Suggestion breaks existing functionality
- Reviewer lacks full context
- Violates YAGNI
- Conflicts with architectural decisions

## Tool Use

Referenced by implementation processes when handling review feedback.