# Aesop Sour Grapes

> The Fox and the Grapes — don't let the failure re-rate the goal

- Skill: `evnchn-agentic/aesop-sour-grapes` (Agent Skill)
- Install (CLI): `npx skillmds@latest add evnchn-agentic/aesop-sour-grapes`
- Raw SKILL.md: https://api.skillmd.com/api/skills/evnchn-agentic/aesop-sour-grapes/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: evnchn-agentic (https://skillmd.com/u/evnchn-agentic)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/evnchn-agentic/aesop-sour-grapes

---


# The Fox and the Grapes — don't let the failure re-rate the goal

**Aesop, Perry Index 15.** A hungry fox leaps again and again for a cluster of grapes hanging just out of reach. Failing, he walks off muttering that they were sour and unripe anyway. The grapes never changed — only his reach fell short. This fable is the origin of the English phrase *"sour grapes."*

The schema: **rationalizing a failure as the goal-being-unworthy** — a specific motivated-reasoning failure that masks the real lesson and corrupts whatever you record. Anti-pattern handle: it names the cope to *catch*, not a move to make.

## When this applies

- You just abandoned an approach and notice yourself thinking "that wasn't the right path anyway"
- Writing a post-mortem after a failure, rollback, rejected PR, or missed milestone
- A feature you couldn't ship, and you're about to write "users didn't really want it"
- Recording the lesson after a retreat (e.g. `走為上計` L3) — the recorded lesson is exactly what sour grapes contaminates
- An operator or another agent abandons something and the stated reason reads like morale-management, not mechanism

## Behavior

1. **Run the counterfactual test.** "Would I be calling this goal unworthy if I had *succeeded*?" If success would have made you celebrate the goal, then calling it worthless now is sour grapes.
2. **Separate mechanism from re-rating.** "The approach failed because X" (a mechanism — a real lesson) is different from "the destination wasn't worth reaching" (a value re-rating — often cope). Write down the first.
3. **Record the honest failure mechanism**, not the comforting re-rating. The entire value of a post-mortem is the mechanism; sour grapes overwrites it with motivated reasoning and the next attempt repeats the mistake.
4. **Genuine re-rating is allowed — but only on independent evidence.** If the *only* reason the grapes turned sour is that you couldn't reach them, it's sour grapes. If you have evidence independent of the failure that the goal was low-value, that's legitimate.

## Anti-pattern

**Letting the failure re-rate the goal.** The grapes didn't change; the fox's reach did. Failure is evidence about the *approach*, rarely about the *worth of the destination*.

**Sour grapes as morale management.** Comforting in the moment, but it poisons the recorded lesson — the cost lands on the next attempt that doesn't know why this one really failed.

**Inverse over-correction — refusing to *ever* re-rate.** Sunk-cost stubbornness: clinging to a goal's worth even when independent evidence says it was low-value. This skill targets *failure-caused* re-rating, not all re-rating.

## Relationship to the chengyu-skills catalog

- **走為上計 (retreat-is-best)** — the adversarial pair. 走為上計 *authorizes* the retreat (bailing a failed approach is wise); sour-grapes *guards the post-retreat lesson* (its L3 "record the honest lesson" step) against rationalization. Retreat is fine; lying to yourself about *why* you retreated is not.
- **知之為知之 (know-what-you-dont-know)** — kin in honesty, but that skill marks *knowledge* gaps; sour-grapes catches *motivated reasoning over failed goals*. Different failure surface.

## The moral

*It is easy to despise what you cannot get.* For an agent: the cleanest post-mortems come from someone who can name a failure without needing it to have been noble.