1. Introduction
In an era where AI agents like Claude Code and GitHub Copilot have become commonplace, the development landscape has undergone a dramatic transformation. Once you issue an instruction, code flows out effortlessly. However, isn't there a lingering issue: do you find yourself repeatedly explaining to the AI—verbally or via chat—what you want built?
This is akin to giving driving directions to a driver (AI) without ever telling them the final destination. While the code you get might work in the moment, after some time passes, you inevitably wonder: "Why is the implementation structured this way?" and "What was the original specification again?" As code and specs gradually diverge, many teams face this problem regardless of project size.
In reality, situations like these are commonplace:
"Specifications don't exist in the first place"
