docs: document Articles IV, V & VI as project-customizable in spec-driven.md#2467
Conversation
|
@copilot apply changes based on the comments in this thread |
Applied all three review comments in d4ec0b7:
|
|
@copilot apply changes based on the comments in this thread |
Match the style of existing articles which state principles and rationale without referencing specific Spec Kit commands.
Replace 'clarification pipeline' tooling references with principle-effect language matching Articles I-III and VII-IX.
Article VI now covers governance and versioning of all project artifacts (constitution, specs, plans, tasks), not just constitution amendments. This matches what spec-driven.md itself describes: specifications versioned in branches, requirement changes propagating across artifacts, and cross-artifact consistency.
Constitution and specifications are the versioned sources of truth. Plans and tasks are derived execution artifacts. Implementation gaps are addressed through new specifications, preserving the feed-forward dependency direction rather than retrofitting code back into specs.
Support all three schools: new spec, update existing spec, or regenerate derived artifacts. The only invariant is that specs drive implementation, not the reverse, and gaps are addressed through specifications rather than untracked code changes.
Constitution uses semantic versioning (major/minor/patch). Specifications use branch-based workflows (feature branches, reviewed and merged like code). Consistent with the existing description in spec-driven.md line 21.
Spec versioning is now tool-agnostic: 'versioned and reviewable before acceptance' rather than prescribing branch-based workflows.
- Remove git branch references from conceptual sections (lines 21, 152) - Remove memory/constitution.md file path from principles section - Replace 'immutable principles' with 'governing principles' to reconcile with Article VI semantic versioning - Constitutional Evolution section now acknowledges principles themselves can evolve through governed process, not just their application
550aaac to
2116770
Compare
|
@copilot apply changes based on the comments in this thread |
Applied all three review comments in the latest commit:
|
|
@copilot apply changes based on the comments in this thread |
Applied both comments in the latest commit:
|
spec-driven.mdclaimed "nine articles" but only documented six — Articles IV, V, and VI were silently missing between Article III and Articles VII & VIII.Changes
spec-driven.md— adds#### Articles IV, V & VI: Project-Specific Standardsbetween Article III and Articles VII & VIII:/speckit.constitution, not as universal fixed requirements/speckit.constitutionsupports fewer or more principles than the template default, and that/speckit.analyzevalidates spec, plan, and task artifacts against every principle in the project constitution/speckit.constitutionas the recommended command for creating or updating the constitution, and to.specify/memory/constitution.mdas the resulting file