Skip to content

docs: document Articles IV, V & VI as project-customizable in spec-driven.md #2467

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Copilot wants to merge 7 commits into
base: main
Choose a base branch
from
+10 −0
Open

docs: document Articles IV, V & VI as project-customizable in spec-driven.md #2467

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
8112291
Initial plan
Copilot May 6, 2026
7fe6448
docs: document Articles IV, V, VI as project-customizable in spec-dri…
Copilot May 6, 2026
d4ec0b7
docs: fix Articles IV–VI section based on review feedback
Copilot May 6, 2026
b9c7a0c
docs: fix PRINCIPLE_5 example hint and constitution template path ref…
Copilot May 6, 2026
88e9823
docs: reconcile PRINCIPLE_5 hint label and standardize constitution p…
Copilot May 6, 2026
ad5d907
docs: point to /speckit.constitution for defining project articles IV-VI
Copilot May 6, 2026
32a90dd
docs: fix PRINCIPLE_5 example hint inconsistency and add tasks.md to …
Copilot May 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions spec-driven.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -318,6 +318,16 @@ No implementation code shall be written before:

This completely inverts traditional AI code generation. Instead of generating code and hoping it works, the LLM must first generate comprehensive tests that define behavior, get them approved, and only then generate implementation.

#### Articles IV, V & VI: Project-Customizable Standards

Articles IV, V, and VI are the primary areas the constitution template reserves for project-specific standards. While the `/speckit.constitution` command lets teams define fewer or more principles than the template provides, these three articles represent the typical customization focus:

- **Article IV** addresses integration concerns—such as integration testing requirements, contract testing across service boundaries, or cross-component communication standards. The constitution template's `[PRINCIPLE_4_NAME]` / `[PRINCIPLE_4_DESCRIPTION]` slot is dedicated to this article, with an example hint of *Integration Testing*.

- **Articles V & VI** address operational and lifecycle concerns—such as observability, structured logging, versioning schemes, or breaking-change policies. By default, the template groups these under a single `[PRINCIPLE_5_NAME]` / `[PRINCIPLE_5_DESCRIPTION]` slot. Teams can name and scope this slot however fits their project, or expand to separate articles using `/speckit.constitution`.

To define these articles for your project, run `/speckit.constitution`—it guides you through populating the principle sections in `.specify/memory/constitution.md`. The `/speckit.analyze` command validates all spec, plan, and task artifacts against every principle in your project constitution, so any rules you define here are automatically applied during analysis.

#### Articles VII & VIII: Simplicity and Anti-Abstraction

These paired articles combat over-engineering:
Expand Down