Temper

This is the antidote to over-engineering. It catches you when you've built a six-agent pipeline for what should be a single prompt, or abstracted a config system before writing any actual features. The best part is the Complexity Test: four questions that force you to justify every component, especially "would removing this break anything?" It's opinionated about what not to cut (error handling, logging, your golden test set) and what usually goes first (premature optimization, abstraction layers with one implementation). Pairs well with evaluate to prove you didn't sacrifice quality while simplifying. Honestly, most teams should run this before their first demo.