Living Specs in SpecKit: Keeping One Current Spec Per Feature

The author, nine months into building a VS Code extension with spec-driven development, found that per-change specs grew into an unread archive. Their SpecKit Companion tool introduces a living spec: a single document per feature, such as billing or auth, describing what it must do today. Each run that touches a feature reads that document before drafting and updates it once the work is complete. This avoids agents re-deriving the same understanding from code every time and makes it easy to see a feature's current behavior. The piece argues that frozen, numbered spec folders become a hard-to-navigate history rather than usable documentation.