I Built a Skill That Writes Your Specs For You

I Built a Skill That Writes Your Specs For You Julián Deangelis published a piece last week that hit 194k views in days. The argument: AI coding agents don't fail because the model is weak. They fail because the instructions are ambiguous. He called it Spec Driven Development. Four steps: specify what you want, plan how to build it technically, break it into tasks, implement one task at a time. Each step reduces ambiguity. By the time the agent starts writing code, it has everything it needs — what the feature does, what the edge cases are, what the tests should verify. The piece is right. The problem is the workflow takes discipline most sessions don't have. Under deadline pressure, the spec step disappears and you're back to prompting directly. So I built a skill that does the spec-writing for you. The silent decisions problem Julián's example stuck with me: "Add a feature to manage items from the backoffice." The agent reads the codebase, picks a pattern, writes the feature. At firs