Evolving specs (2025)
The discussion revolves around the challenges of managing specifications in software development. Participants debate whether to update the master spec or create new specs for changes. The conversation highlights differing opinions on the role of specifications versus code as the source of truth.
- ▪Ian1971 initiated a conversation about handling change requests in spec-driven development.
- ▪SimonGartz suggested that new features should be added as separate specs rather than altering the master spec.
- ▪RobertDouglass emphasized that the code itself should be the primary source of truth, while Rosmur argued for the importance of human oversight in code management.
Opening excerpt (first ~120 words) tap to expand
github / spec-kit Public Notifications You must be signed in to change notification settings Fork 9k Star 102k Code Issues 280 Pull requests 146 Discussions Actions Projects Models Security and quality 0 Insights Additional navigation options Code Issues Pull requests Discussions Actions Projects Models Security and quality Insights Evolving specs #152 Ian1971 started this conversation in General Evolving specs #152 Ian1971 Sep 10, 2025 · 38 comments · 82 replies Return to top Discussion options Uh oh! There was an error while loading. Please reload this page. {{title}} Something went wrong. Uh oh! There was an error while loading. Please reload this page. Quote reply Ian1971 Sep 10, 2025 - Using the spec kit I create a spec and implement it.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.