A standing assumption-testing prior for Claude Code — before adopting a borrowed component or accepting an asserted limit, name it as a falsifiable claim and test whether the constraint is load-bearing HERE or cargo-culted.
Before the model adopts a borrowed component or accepts an asserted limit, it names the assumption as a falsifiable claim and checks whether the constraint is actually load-bearing in this regime — or cargo-culted from a different one.
The external sibling of flip-the-script: that plugin distrusts the model's own recall; this one distrusts inherited assumptions. Both route to measured ground truth instead of authority.
/plugin marketplace add 88plug/claude-code-plugins
/plugin install break-dogma@88plug
grok plugin marketplace add 88plug/claude-code-plugins
grok plugin install break-dogma@88plug --trust
No further wiring — the hooks are declared inline in the manifest and load automatically once the plugin is enabled.
| Hook | Event | What it does |
|---|---|---|
prime.sh |
SessionStart |
Injects the assumption-testing posture once per session |
nudge.sh |
UserPromptSubmit |
Fires only when the prompt carries assumption / asserted-limit / borrowed-component language; silent on mechanical requests |
The full mining + break procedure — the four dogma kinds, the gh/searxng/repomix
recipes, the case log, the honesty guard — is in the bundled break-dogma skill.
- Name the assumption as a testable sentence — "X is necessary for Y in this regime."
- Mine its origin and the regime that made it real (competitor issues/PRs/RFCs, searxng, repomix, deepwiki).
- Test load-bearing here vs cargo-culted from another regime. An asserted limit is a hypothesis — name its number, measure it.
- Break what isn't load-bearing and build in the space it guarded; keep + log what survives.
Reuse leaves that aren't the moat — reinventing them is its own dogma. A surviving assumption is a first-class result: "we tested it and it holds" stops the next person re-litigating it. Never break on authority in either direction; the only reason is the measured or architectural test.
- flip-the-script — internal-recall sibling of this external-assumption prior.
- read-the-damn-docs — the verification route when the assumption is version/API/library.
- scientific-method — an asserted limit becomes a falsification probe.
- world-first — a broken load-bearing constraint is the removed-constraint entry point.
bash tests/smoke.sh # prime always injects; nudge fires on dogma-language, silent otherwiseFSL-1.1-ALv2.