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

docs: remove /speckit.* command references from Articles IV-VI

Browse Source 
Match the style of existing articles which state principles and
rationale without referencing specific Spec Kit commands.
This commit is contained in:
Manfred Riem
2026-05-11 09:26:13 -05:00
parent 423e104835
commit 8f87999daf
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
spec-driven.md
View File

@@ -329,7 +329,7 @@ All requirements MUST be:
- Traceable: mapped from user stories through tasks to implementation
```
This article drives the clarification, checklist, and analysis pipeline. The `/speckit.clarify` command scans for ambiguity across functional scope, data modeling, interaction flows, and edge cases. The `/speckit.checklist` command generates "unit tests for English"—validating requirement quality rather than implementation correctness. The `/speckit.analyze` command performs cross-artifact consistency checks, catching coverage gaps, terminology drift, and duplicate or conflicting requirements before any code is written.
This article drives the clarification, checklist, and analysis pipeline. Before planning begins, specifications are scanned for ambiguity across functional scope, data modeling, interaction flows, and edge cases. "Unit tests for English" validate requirement quality rather than implementation correctness. Cross-artifact consistency checks catch coverage gaps, terminology drift, and duplicate or conflicting requirements before any code is written.
#### Article V: Non-Functional Standards
@@ -343,7 +343,7 @@ Non-functional requirements MUST be specified for:
- Accessibility: interaction standards for all user interfaces
```
Without this article, LLMs default to functional-only implementations—code that works but cannot be monitored, secured, or maintained in production. The clarification pipeline explicitly scans for non-functional coverage gaps, and checklists can target specific quality dimensions (security, performance, UX) to ensure these concerns are captured in requirements before implementation begins.
Without this article, LLMs default to functional-only implementations—code that works but cannot be monitored, secured, or maintained in production. The clarification pipeline explicitly scans for non-functional coverage gaps, and checklists can target specific quality dimensions to ensure these concerns are captured in requirements before implementation begins.
#### Article VI: Governance and Versioning
@@ -356,7 +356,7 @@ Constitution amendments MUST:
- Maintain cross-artifact consistency after every change
```
This article ensures that governance is not static. When principles evolve, the `/speckit.constitution` command validates that plan templates, spec templates, task templates, and command files remain aligned. Version bumps are classified by impact—major for removed or redefined principles, minor for additions, patch for clarifications—creating an auditable trail of architectural decisions.
This article ensures that governance is not static. When principles evolve, plan templates, spec templates, task templates, and command files must remain aligned. Version bumps are classified by impact—major for removed or redefined principles, minor for additions, patch for clarifications—creating an auditable trail of architectural decisions.
#### Articles VII & VIII: Simplicity and Anti-Abstraction