principle-attack-the-premise

Original：🇺🇸 English

Translated

Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.

2installs

Sourcemariusflorescu/pstack-t3

Added on2026-11-01

NPX Install

npx skill4agent add mariusflorescu/pstack-t3 principle-attack-the-premise

SKILL.md Content

View Translation Comparison →

Attack the Premise

When two or more fixes that share one premise have failed the same gate, suspect the premise, not the fixes.

Why: Each failed fix is evidence against the belief it assumed. A third fix on the same premise spends effort where the evidence already says the cause is not.

Pattern:

Write the premise down. The premise is the one sentence that every failed fix assumed.
Test the premise before the next fix. Find an observation that would come out differently if the premise were false, and make it. Look at how the failures are distributed, not only at how large they are. Make the check rerunnable per Build the Lever.
Follow the evidence. If it contradicts the premise, the cause is elsewhere. Look for what the failures have in common that the premise did not predict. If it confirms the premise, ask the next "why" per Fix Root Causes. The earlier fixes may have treated a consequence instead of the cause.
Remove the condition instead of compensating for it, per the Laziness Protocol. If the evidence shows that one part always lands on the losing side, change what puts it there. A mechanism that cleans up after it leaves the cause in place and adds work on every run.

Stop: Do not start the next fix before the premise is written down and tested.

This principle is distinct from Redesign from First Principles, which rebuilds a design around a new requirement. It questions a fact the current design assumes.

principle-attack-the-premise

NPX Install

Tags

SKILL.md Content

Attack the Premise