Developer Built 238 Specs for a VS Code Extension and Found Them Useless

A developer spent nine months building a VS Code extension called SpecKit Companion using spec-driven development, generating 94 spec folders and 238 markdown files totalling over 15,000 lines. The approach, built on GitHub's spec-kit, requires an AI agent to document intent before writing any code, moving features through specify, plan, tasks, and implement phases. While the method successfully prevented vague requirements from becoming faulty code, the developer found that accumulating dozens of specs created an unmanageable archive rather than useful documentation. Multiple specs often covered the same evolving feature, with no clear indication of which were current, turning the specs folder into what the author called an archaeological site of contradictions. The developer also observed that their AI coding agent ignored the specs entirely, opting instead to reconstruct intent directly from the codebase each session.