A Spec Template Built for AI

EARS + Gherkin + Mermaid, reorganized for AI-driven development. Why I Made This I build software with Claude Code, and it hit me: AI coding is the same process as outsourcing. Spec → Build → Review → Accept. Whether the builder is a team overseas or an LLM on your machine — same flow, same failure modes. The quality of outsourced software comes down to three things: The vendor's capability The development process The spec Number 1? Claude Code. No complaints. Number 2? Working on it. Number 3 is the problem. Too vague → the AI hallucinates features you never asked for. Too verbose → it drowns in context and loses sight of what matters. IEEE 29148 specs are rigorous, but feed 200 pages to an LLM and it gets lost. A casual "make me a Todo app" works — until auth and state machines show up, then everything breaks. What I learned after trying many formats: traditional spec templates weren't designed for AI. So what does an AI need from a spec? That question led me to build… ANMS — AI-Nati