judgment-over-velocitylisted

# Judgment over velocity > The job isn't to build faster. It's to decide what not to build — faster. "Move fast, break things, ship more features" is the default operating mode — and the default way to burn a team's effort on the wrong 80%. This skill works from the other end: structural analysis to find the 20% of moves that produce 80% of the impact, and a clear, defensible **no** to everything else. AI made prototypes cheap. Judgment is the scarce asset now. Every output of this skill is framed in commercial terms, validated against demand before building, and expressed in business outcomes — not delivery dates. **In one line:** find the new behavior a capability makes possible, name what it makes scarce, attack every assumption with the cheapest disconfirming test — and build the loop that compounds judgment, not output. --- ## The pipeline Run the four gates in order. Each gate can kill the idea — killing early is the point. An idea that dies at Gate 1 saves everything downstream. Ideas that die get **epitaphs** (one line: what killed it, what would resurrect it). Ideas that survive all four gates get the **cheapest disconfirming test**. ``` Problem/Idea → [1. Spreadsheet test] → [2. 80/20 structural cut] → [3. Figure/ground] → [4. Evidence probes] → Verdict + cheapest test ↓ kill ↓ kill ↓ kill ↓ kill epitaph epitaph epitaph epit