principle-attack-the-premise
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. Use for /principle-attack-the-premise.
- License 许可
- MIT
- 所属仓库
- lovrozagar/grunt
- 最近更新
- 2026-11-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- principle-attack-the-premise
- description
- 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. Use for /principle-attack-the-premise.
03 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.
Slash /principle-attack-the-premise only. Not a session flag.
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
/principle-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
/principle-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
/principle-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 /principle-redesign-from-first-principles, which rebuilds a design around a new requirement. It questions a fact the current design assumes.
04 同仓库更多 Skills
write-roadmap
Write an ordered program of plans under .tmp/grunt/roadmaps/. Use for /write-roadmap. Stops for y, which locks and runs it.
write-plan
Write a local checklist under .tmp/grunt/plans/. Then /implement-plan {n}.
unslop
Cut AI tells from any writing. Use for /unslop.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file, or for /typescript-best-practices.
tmp
Dump a one-off convo artifact under .tmp/grunt/.
teach
Explain a body of work plainly so a person actually understands it. Dig into how it works and why it is that way, then weave that into one clear explanation. Use for /teach, 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.