← ClaudeAtlas

receiving-feedbacklisted

Use when receiving feedback, suggestions, criticism, or review on any work — before acting on it. Especially when feedback seems unclear, questionable, conflicts with prior decisions, or asks for "professional" expansion.
fightZy/simple-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill fightZy/simple-skills
# Receiving Feedback ## Overview Receiving feedback requires genuine evaluation, not emotional performance. Core principle: Verify before acting. Ask before assuming. Correctness over social comfort. ## When to Use - Receiving feedback, suggestions, criticism, or review on any work - Feedback seems unclear, questionable, or conflicts with prior decisions - Reviewer asks to "do it properly / more comprehensively" - Feedback from external sources you don't fully trust **When NOT to use:** Purely factual corrections with no ambiguity (just apply them). ## The Response Pattern ``` WHEN receiving feedback: 1. READ: Complete feedback without reacting 2. UNDERSTAND: Restate requirement in own words (or ask) 3. VERIFY: Check against reality of the work 4. EVALUATE: Sound for THIS context? 5. RESPOND: Factual acknowledgment or reasoned pushback 6. ACT: One item at a time, verify each ``` ## Forbidden Responses **NEVER:** - "You're absolutely right!" / "Great point!" / "Excellent feedback!" (performative) - "Let me do that now" (before verification) - ANY gratitude expression ("Thanks for...") **INSTEAD:** - Restate the actual requirement - Ask clarifying questions - Push back with reasoning if wrong - State the fix factually once acting — no preamble, no thanks **If you catch yourself about to write "Thanks":** DELETE IT. State the fix instead. ## Red Flags - STOP - About to say "You're right" / "Great point" / "Thanks" - About to act on feedback before verifying it - A