principle-attack-the-premise

Diagnose failed fixes by questioning the shared premise behind them.

4|1|Updated Dec 16, 2023
One-click install
npx skills add https://github.com/Shtian/AuthentiClash --skill principle-attack-the-premise-shtian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-attack-the-premise
Source: https://github.com/Shtian/AuthentiClash/tree/main/.claude/skills/principle-attack-the-premise
Command: npx skills add https://github.com/Shtian/AuthentiClash --skill principle-attack-the-premise-shtian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple fixes built on the same assumption keep failing the same gate, this Skill redirects debugging effort from writing yet another fix to questioning the underlying premise that all the failed fixes shared. ## Core Features & Use Cases - Premise Identification: Write down the single sentence that every failed fix assumed, turning repeated failures into evidence about that assumption. - Actor Census: Run a rerunnable census script that counts which actors hold the imbalance, revealing whether the same few actors are assigned the problematic role on every run. - Asymmetry Removal: Rotate, randomize, or relocate the role instead of adding compensating mechanisms like return paths, shared pools, or periodic rebalances. - Use Case: Imagine a load-balancing bug where three consecutive fixes failed and the same two servers keep receiving most of the traffic. Use this Skill to write down the premise, census the traffic per server, find what assigns those servers that role, and remove the asymmetry. ## Quick Start Ask the AI to apply the attack-the-premise principle to a bug where two or more fixes sharing one assumption have already failed the same test or 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. Repeated failures under a shared premise are evidence about the premise itself, not the individual fixes.

What is a premise census in debugging?▼

A premise census is a rerunnable script that counts the imbalance per actor in a system. It shows which actors hold the imbalance rather than how large it is, revealing whether the same few actors are assigned the problematic role on every run.

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

Question the premise when two or more fixes that share one assumption have failed the same gate. Do not start the next fix until the premise is written down and a census of the imbalance exists.

What if the census shows the imbalance is even across actors?▼

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

Why remove asymmetry instead of compensating for it?▼

Compensating mechanisms like return paths, shared pools, batched hand-offs, or periodic rebalances leave the faulty role assignment in place and add work on every run. Rotating, randomizing, or moving the role removes the root asymmetry so no actor holds it permanently.