Learn more about scope trimming and the decision ledger.
How the Skill Works
What does this skill do exactly?
The scope-trimming skill takes an idea or half-built project, evaluates it against clear criteria, and gives you a binary verdict: Ship (full commit), Cut (remove), or Kill (scrap entirely). No debate, just a decision. It then logs that decision to an audit ledger so future you can reference it.
What's the "ledger" and why does it matter?
The ledger is a signed markdown file in your .enough/ folder that records each scope verdict with a timestamp, your name, a deadline, and a kill criterion. It prevents re-litigating scope decisions. When you're tempted to rebuild something you cut in March, the ledger quotes your own past reasoning back at you.
How does drift audit mode work?
Drift audit runs a grep across your repo for code matching your cut decisions. If it finds a file you said you were removing, it quotes your original verdict back: "/src/compare/ exists, but you cut this on March 12." This catches scope creep before it ships.
Using the Ledger
When should I refer back to the ledger?
Consult the ledger whenever you're tempted to rebuild or re-implement something. It's your best defense against scope creep and endless re-litigating. Also run it regularly (monthly or quarterly) to audit actual vs. decided state.
Can I override a past decision?
Yes. If circumstances change and you have new evidence (a paying customer request, a rung-4 reason), you can override. But the ledger tracks that override, so you can look back and see when your judgment shifted and why.
What counts as a "rung-4 reason" to rebuild something?
A paying user asked for it, or your metrics show concrete demand. Not "it would be cool" or "someone in Slack mentioned it." The bar is intentionally high so you don't waste time re-litigating weakly justified cuts.
Getting Started
How do I start using this skill?
1. Create a .enough/ folder in your repo. 2. Ask the skill about an idea or feature. 3. Read the verdict. 4. Approve it to sign the ledger entry. The ledger persists and is consulted on future decisions.
What if I'm not ready to commit to a decision?
You can ask for an analysis without signing the ledger. The skill will explain the reasoning, but won't create a binding record. When you're ready to lock in, approve and it signs.
Do I need to use this for every feature?
No. Use it for big decisions that you're likely to second-guess. Small bugfixes or obvious features don't need ledger entries. It's designed for the high-stakes scope calls where memory failure costs time.
Pricing & Access
What does this skill cost?
This is a Claude skill. It runs inside Claude, so cost depends on your Claude usage. No separate subscription or per-decision fees.
Can I use this in teams?
Yes. Multiple team members can invoke the skill on the same repo. Each verdict is signed with a name, so the ledger tracks who decided what and when.