agentleFS
Sign inStart free
3metaJun3metaJun/mstack/skills/principle-attack-the-premise/SKILL.md

principle-attack-the-premise

Skill0 starsChanged 27 days agoMITView on GitHub

Apply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it.

We split this skill into the rules it gives an agent

4 rules. 2 are common, 2 are distinctive, and 0 are very specific to this project.

  • 2

    Common

    Most of the 30 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

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

    line 8
  2. Distinctive:

    Read the skew: If the same few actors hold most of the imbalance on every run, something assigns them that role.

    line 15
  3. Common:

    Do not start the next fix before the premise is written down and the census exists.

    line 19
  4. Distinctive:

    If the census is even across actors, the premise is not the cause.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 30 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 failure under a shared premise is evidence about the premise.

Pattern:

  • Write the premise down. The premise is the one sentence that every failed fix assumed.
  • Take a census before the next fix. Count the imbalance per actor. The census shows which actors hold the imbalance, not how large it is. Write the census as a rerunnable script per Build the Lever.
  • Read the skew. If the same few actors hold most of the imbalance on every run, something assigns them that role. Find what assigns the role. That assignment is the next "why" per Fix Root Causes.
  • Remove the asymmetry instead of compensating for it, per the Laziness Protocol. Rotate the role between actors, randomize the assignment, or move the role, so that no actor holds it on every run. A return path, a shared pool, a batched hand-off, or a periodic rebalance leaves the assignment in place and adds work on every run.

Stop:

  • Do not start the next fix before the premise is written down and the census exists.
  • If the census is even across actors, the premise is not the cause. Look for the cause elsewhere and keep the census as evidence.

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free