principle-attack-the-premise

Diagnose repeated fix failures by questioning the shared premise behind them.

1|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/edivad1999/stuc-stack --skill principle-attack-the-premise-edivad1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-attack-the-premise
Source: https://github.com/edivad1999/stuc-stack/tree/main/skills/principle-attack-the-premise
Command: npx skills add https://github.com/edivad1999/stuc-stack --skill principle-attack-the-premise-edivad1999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When two or more fixes that share one assumption keep failing the same gate, writing another fix under the same premise wastes effort. This Skill redirects debugging toward questioning the premise itself and locating which actors hold the imbalance. ## Core Features & Use Cases - Premise Identification: Write down the single sentence every failed fix assumed, turning implicit assumptions into testable statements. - Actor Census: Build a rerunnable script that counts the imbalance per actor, revealing which actors consistently hold the skewed role. - Asymmetry Removal: Rotate, randomize, or relocate the role instead of adding compensating work like return paths or periodic rebalances. - Use Case: A load-balancing fix keeps failing because the same few workers always receive the heaviest tasks. Instead of a third retry fix, run a census, find what assigns that role, and remove the asymmetry. ## Quick Start Ask the AI to apply the attack-the-premise principle to a bug where multiple fixes have failed the same test gate.

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 debug when multiple fixes keep failing the same test?▼

Write down the one 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 most of the imbalance on every run, find what assigns them that role.

What is a premise census in root cause analysis?▼

A census is a rerunnable script that counts the imbalance per actor in the system. It shows which actors hold the imbalance rather than how large it is, providing evidence about whether the shared premise is the actual cause.

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.

What if the census shows an even distribution across actors?▼

If the census is even across actors, the premise is not the cause of the failures. Look for the cause elsewhere in the system and keep the census results as evidence for future investigation.

How is attacking the premise different from redesigning from first principles?▼

Attacking the premise questions a fact the current design assumes, while redesigning from first principles rebuilds a design around a new requirement. Use premise attack for repeated fix failures, not requirement changes.