github/github-spec-kit
1
0
Fork 0
mirror of https://github.com/github/spec-kit.git synced 2026-07-03 20:36:23 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: remove git branch implementation detail from Article VI

Browse Source 
Spec versioning is now tool-agnostic: 'versioned and reviewable
before acceptance' rather than prescribing branch-based workflows.
This commit is contained in:
Manfred Riem
2026-05-11 09:40:24 -05:00
parent 25175e2121
commit e3bcefdfcb
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
spec-driven.md
View File

@@ -358,7 +358,7 @@ Governance MUST ensure:
This article ensures that governance is not static and that specifications remain the authoritative source. When a gap or requirement emerges during implementation, teams may create a new specification, update an existing one, or regenerate derived artifacts—whichever approach fits their workflow—as long as the specification continues to drive implementation rather than the reverse.
The constitution follows semantic versioning—major for removed or redefined principles, minor for additions, patch for clarifications. Specifications are versioned through branch-based workflows—each feature specification lives in its own branch and is reviewed and merged like code. Together, these models create an auditable trail of architectural and product decisions.
The constitution follows semantic versioning—major for removed or redefined principles, minor for additions, patch for clarifications. Specifications must be versioned and reviewable before acceptance. Together, these practices create an auditable trail of architectural and product decisions.
#### Articles VII & VIII: Simplicity and Anti-Abstraction