vanguard-spec: Locking down architectural invariants before line one
I used to be skeptical of spec-driven development with AI.
In most teams, the workflow looks the same: prompt an LLM with a product requirement, wait ten seconds, and get back a 30-page markdown document. It has every architectural heading imaginable, but nobody actually reads it. You jump straight from an initial prompt to an exhaustive document, skipping the deliberate pushback where design risk actually gets eliminated.
Things changed for me when I started using Dave Rensin’s Elephant-Goldfish Model (EGM).