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.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/github/spec-kit/discussions/152 |
| Publication time | Tue, 19 May 2026 07:48:02 +0000 |
| Retrieval time | 2026-05-19T08:04:57.437Z |
| Last seen | 2026-05-19T08:04:57.437Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | v_QcyuRwhsDn |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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.