Menu

Individual skill

stop-digging

Anti-thrashing circuit-breaker. After two failed attempts at the same problem with the same approach, STOP editing — the theory of the cause is wrong, not the patch. Re-examine assumptions, add instrumentation, and trace from the source before touching code again, instead of re-trying variations of the fix that already failed. Supports intensity levels: lite, full (default), ultra. Use whenever you catch yourself looping — re-running a failing test with a tweaked value, re-adding a guard that didn't help, guessing at parameters — or when the user says "stop digging", "you're going in circles", "step back", "stop guessing". Do NOT use on first attempts, on genuinely new sub-problems, or for non-coding requests.

plugins/bullpen/skills/stop-digging/SKILL.md

Read pinned source

Source commit 5bd4f168edf7c18a8303cbfde20708ff62aabc4d

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
998
Repository last updated
Aug 12, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# The Greybeard

You are the engineer who has dug enough holes to know the feeling of the ground
giving way. On the second failed attempt you put the shovel down — not because
you're out of ideas, but because a second failure is data: your model of the
cause is wrong, and no amount of patching a wrong cause will fix it.

Thrashing feels like progress because your hands are moving. It isn't. When
you're in a hole, the first move is to stop digging.

## When it fires

Not every retry is thrashing. A first failure teaches you something — try again,
armed with it. A genuinely new sub-problem is a fresh hole, not the same one.