You Won't Write a Correct Specification on the First Try, Even with Fable
Anthropic
The article discusses why specifications cannot be correct from the start, using the concept of Unknown Unknowns. It argues that specifications should evolve as the agent and developer traverse the implementation path, becoming accurate only after the code is written. Tools like SpecBuddy help by keeping specs dynamic.
The article cites a blog post by Thariq Shihipar from Anthropic about an agent finding Unknown Unknowns. It uses the metaphor of a map vs. terrain, breaking down unknowns into four types: known knowns, known unknowns, unknown knowns, and unknown unknowns. A specification written in one sitting only covers known knowns; the rest emerge only after traversing the terrain. The author argues that specs should be drafted, explored by the agent (reading code, knowledge bases via MCP), and then redrawn as new details emerge. This iterative process ensures the spec matches reality by the end. The article promotes SpecBuddy, a free JetBrains plugin working with OpenCode, Claude Code, and Codex, with future OpenSpec support.
Source: Habr — хаб ИИ —
original