From grimoire
Defines 'enough' as an explicit target before starting, grounded in satisficing theory and behavioral economics, to prevent over-optimization and improve decision outcomes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:apply-sufficiency-thresholdThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Define "enough" as an explicit target before you begin — and stop when you reach it — because optimizing without a defined endpoint produces worse outcomes, higher risk, and lower satisfaction than satisficing with a clear sufficiency threshold.
Define "enough" as an explicit target before you begin — and stop when you reach it — because optimizing without a defined endpoint produces worse outcomes, higher risk, and lower satisfaction than satisficing with a clear sufficiency threshold.
道德经 Chapters 33 and 46 (Laozi, ~6th–4th century BC):
知足者富。(Chapter 33) — Those who know enough are wealthy.
祸莫大于不知足;咎莫大于欲得。故知足之足,常足矣。(Chapter 46) — There is no greater disaster than not knowing when enough is enough; no greater fault than wanting more. Knowing the sufficiency of sufficiency: this is always sufficient.
Why best: Laozi's observation is not a moral instruction to be satisfied with less — it is a causal diagnosis: the greatest strategic failures come not from insufficient ambition but from not defining the endpoint. Those who know what "enough" looks like stop at the right moment; those who don't overrun their position, take on excess risk, and lose what they accumulated.
Herbert Simon — satisficing theory (1956, Nobel Prize in Economics 1978): Simon coined "satisficing" (satisfy + suffice) to describe the decision strategy of searching for a solution that meets a defined threshold rather than optimizing for the maximum. His finding: in complex real-world decisions with incomplete information, satisficing consistently produces better outcomes than maximizing because: (1) the cost of searching for the optimal solution often exceeds the benefit of the optimum over a good-enough solution; (2) the "optimal" solution identified under incomplete information is often not actually optimal; (3) maximizing behavior produces decision fatigue, regret, and delayed action. Simon's satisficing model is standard in organizational theory, behavioral economics, and decision science. His work is the theoretical foundation for "good enough" as a rigorous decision criterion.
Barry Schwartz — "The Paradox of Choice" (2004, 2M+ copies): Schwartz's empirical research demonstrates that maximizers (people who seek the best possible option) are systematically less happy, more anxious, and more regretful than satisficers (people who seek a good-enough option). Key finding: more options and more optimization time produce worse subjective outcomes, not better ones. Paradoxically, the person who stops searching when they find "good enough" ends up more satisfied than the person who searches for the optimum. Applied in product design (fewer options improve conversion), choice architecture (default design), and behavioral finance.
Morgan Housel — "The Psychology of Money" (2020, 3M+ copies): Housel dedicates an early chapter to "enough" as the central concept in financial decision-making. His observation: the most common financial catastrophes involve people who accumulated more than most people ever will, then lost it — not because they were unlucky but because they didn't have a defined "enough" threshold and kept pressing. His examples: Rajat Gupta (insider trading for money he didn't need), Bernie Madoff (fraud sustained long past any rational "enough" point), and many others. Housel's argument: defining your "enough" number in advance is a risk management tool, not a contentment practice.
Kurt Vonnegut / Joseph Heller anecdote: Vonnegut asked Heller how he felt knowing that a hedge fund manager at the party they were attending earned in a single day what Heller's novel "Catch-22" had earned in its entire history. Heller replied: "I have something he will never have — enough." This exchange became widely cited in finance and management literature as the clearest articulation of why the sufficiency threshold matters: without knowing what "enough" is, "more" has no endpoint.
Warren Buffett on not knowing when to stop: Buffett has repeatedly observed that the most common failure mode among successful people is not knowing when to stop: "The most important thing to do if you find yourself in a hole is to stop digging." And: "I've never met someone who was truly happy because they didn't take that last deal." The absence of a defined sufficiency threshold is what keeps successful people in accumulation mode past the point where additional accumulation produces any improvement in outcomes.
Why distinct from apply-peak-exit: apply-peak-exit triggers when you hold a winning position and need to determine the optimal timing to exit — it is about the signal conditions for stopping. apply-sufficiency-threshold is about defining what "enough" looks like BEFORE you start, so that reaching the threshold is a recognized success condition rather than a reason to continue. Peak-exit is reactive (you're in a position and timing your exit); sufficiency-threshold is prospective (you haven't started yet, and you're defining the endpoint).
Why distinct from apply-smart-goals: apply-smart-goals ensures that goals are specific, measurable, achievable, relevant, and time-bound — that goal clarity enables execution. apply-sufficiency-threshold addresses a different problem: you may have a perfectly clear goal and still not know when to stop, because you continue optimizing past the goal. The skill is defining "enough" as the success condition, not just the goal as a target.
Adopted by: Warren Buffett and Berkshire Hathaway (explicit "enough" discipline applied to investment exits and business acquisition criteria); Herbert Simon's satisficing model — standard in organizational theory, behavioral economics, and decision science; Barry Schwartz's paradox of choice findings adopted in product design (fewer options improve conversion) and choice architecture globally.
Impact: Herbert Simon's satisficing research (Nobel Prize in Economics 1978) demonstrated that satisficing consistently produces better real-world outcomes than maximizing in complex decisions with incomplete information; Schwartz's empirical research showed maximizers are systematically less happy, more anxious, and more regretful than satisficers, with the person stopping at "good enough" ending up more satisfied than the person searching for the optimum.
Define your sufficiency threshold before beginning. Before starting any optimization, pursuit, or acquisition, answer: "At what level of outcome would I stop and say this is enough?" The definition must be:
Distinguish the threshold from the target. A target ("grow revenue to $10M") is a goal you're working toward. A sufficiency threshold is the level at which you'd stop pursuing more even if more were available. In many decisions, these are the same. In others, they're different: you may target $10M revenue but your sufficiency threshold is "profitable with enough runway to build the next product" — you wouldn't burn cash chasing $10M if $6M profitable met the threshold.
Apply the threshold test to the current decision. When deciding whether to continue, ask the threshold test: "Has the current outcome met my sufficiency threshold?" If yes: stop. Do not re-evaluate the threshold because progress looks good. The point of pre-commitment is that it prevents rationalization at the moment of decision.
Identify and counter the psychological barriers to stopping. The barriers to stopping at sufficiency are predictable:
Apply sufficiency threshold to time, not just outcomes. Many optimization processes run indefinitely because they measure output quality but not time invested. Define a time-based sufficiency threshold too: "I'll spend X hours on this decision; when X hours are spent, I'll accept the best option found so far." Simon's research shows that time-bounded satisficing (stop after X search effort) produces better real-world outcomes than open-ended maximizing.
Revisit thresholds only on principle, not on current progress. A threshold set when you started should not be revised because you are making progress and further progress seems available. Revising upward because progress is good is the failure mode this skill prevents. Revise thresholds only when the underlying conditions that produced the original threshold have changed significantly (the goal context has shifted, not just the current outcome level).
Career/compensation: An executive pre-commits: "My sufficiency threshold is $X total compensation; once I reach it, I won't take on more stress, more risk, or longer hours for additional compensation." Five years later, the threshold is reached. A high-risk opportunity offers a potential 3× increase. Applying the threshold: the opportunity requires accepting a significant probability of losing what was accumulated. The threshold test makes the decision clear: enough is already achieved; the risk is not justified by need.
Product optimization: A team is A/B testing a checkout flow. Pre-committed threshold: "We'll stop testing when we achieve a 15% improvement in conversion." After 4 tests, they've achieved 17%. The team wants to continue because further improvement seems achievable. Applying the threshold: 17% exceeds the 15% threshold. Stop. Redirect engineering to the next product area. Continuing to optimize a metric past its threshold is opportunity cost, not improvement.
Fundraising: A startup founder defines a sufficiency threshold: "We need $3M to build the product and reach revenue. We'll stop fundraising at $4M." Investors offer $8M. Applying the threshold: $4M meets the threshold. Additional capital creates shareholder dilution and investor expectations that are not warranted by the current plan. Founder closes at $4M, declines additional capital. Company avoids over-hiring and mission drift that typically follows excess capital.
Competitive market entry: A company is entering a new market. Sufficiency threshold: "We need 15% market share to be viable; above 30% the defense costs exceed the returns." After 2 years at 22% share, a competitor weakens and 40% share is available. Applying the threshold: 22% already exceeds the 15% threshold; 40% exceeds the 30% upper bound. Hold at 22%. Redirect competitive resources to the next market. Avoid over-investing in defending a position beyond its economic optimum.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireSets a 'good enough' threshold to stop indefinite searches or investigations, saving budget on low-stakes decisions.
Identifies when to exit a winning position before it declines, using optimal stopping theory and decision science. Useful for knowing when to stop investing in a profitable initiative.
Guides defining kill criteria, go/no-go gates, and exit ramps for projects. Helps avoid sunk cost fallacy and make disciplined continue/pivot/kill decisions.