principle-attack-the-premise

Questions the shared premise behind repeatedly failed fixes using an actor imbalance census.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jeremybrasher/grokbot-skills --skill principle-attack-the-premise-jeremybrasher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-attack-the-premise
Source: https://github.com/jeremybrasher/grokbot-skills/tree/main/collections/pstack/skills/principle-attack-the-premise
Command: npx skills add https://github.com/jeremybrasher/grokbot-skills --skill principle-attack-the-premise-jeremybrasher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When two or more fixes built on the same assumption keep failing the same gate, teams often write yet another fix instead of questioning the underlying premise. This Skill interrupts that loop by forcing the premise to be written down and by taking a census of which actors hold the imbalance before any new fix is attempted. ## Core Features & Use Cases - Premise Extraction: Writes down the single sentence every failed fix assumed, turning an implicit belief into a testable claim. - Actor Imbalance Census: Counts which actors hold the imbalance per run, implemented as a rerunnable script, to reveal who is repeatedly assigned the problematic role. - Asymmetry Removal: Rotates, randomizes, or relocates the role instead of adding compensating work like return paths or periodic rebalances. - Use Case: A queue consumer keeps overloading the same worker despite three retry and throttling fixes. Apply this Skill to write down the premise, census the load per worker, discover the scheduler assigns the role, and rotate the assignment instead of adding another patch. ## Quick Start Ask the agent to apply the attack-the-premise principle to your repeated failure, providing the failed fixes, the shared gate, and the decision this analysis should change.

Frequently Asked Questions about principle-attack-the-premise

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop repeated fixes from failing the same way?▼

Write down the single premise every failed fix assumed, then take a census of which actors hold the imbalance before attempting another fix. If the same few actors hold the imbalance on every run, find what assigns them that role and remove the asymmetry.

What is an actor imbalance census in root cause analysis?▼

It is a rerunnable count of which actors hold the imbalance in a system, showing who carries the problematic role rather than how large it is. A skewed census points to the assignment mechanism as the next root cause to investigate.

When should I question the premise instead of writing another fix?▼

Question the premise when two or more fixes sharing one assumption have failed the same gate. Each failure under a shared premise is evidence about the premise itself, not about the individual fixes.

When should I not use the attack-the-premise approach?▼

Do not use it when the trigger condition is not met, when a narrower operational skill covers the same decision, or when the census shows the imbalance is evenly distributed across actors. An even census means the premise is not the cause.

How does attacking the premise differ from redesigning from first principles?▼

Attacking the premise questions a fact the current design assumes, while redesign from first principles rebuilds a design around a new requirement. The former targets a false assumption; the latter targets a changed goal.