docs: document Articles IV, V & VI as project-customizable in spec-driven.md by Copilot · Pull Request #2467 · github/spec-kit

Copilot · 2026-05-06T13:51:17Z

spec-driven.md claimed "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-Customizable Standards between Article III and Articles VII & VIII:
- Identifies each article's domain: IV → integration concerns, V → observability/operational concerns, VI → versioning/lifecycle concerns
- Explicitly marks these as project-defined (unlike I–III and VII–IX, which are framework-fixed)
- References the [PRINCIPLE_4_NAME] / [PRINCIPLE_5_NAME] placeholders in templates/constitution-template.md as the customization point
- Notes that /speckit.analyze already validates dynamically against whatever a project defines — no Spec Kit changes required to extend these articles

…ven.md Agent-Logs-Url: https://github.com/github/spec-kit/sessions/a5a938bd-4400-4deb-bdc8-0109b0bf4ccb Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot

Copilot's findings

Files reviewed: 1/1 changed files
Comments generated: 3

mnriem · 2026-05-06T19:21:50Z

@copilot apply changes based on the comments in this thread

Agent-Logs-Url: https://github.com/github/spec-kit/sessions/2501d2e9-fbcf-4d44-afe1-1fa19f1a0a24 Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot · 2026-05-06T19:24:19Z

@copilot apply changes based on the comments in this thread

Applied all three review comments in d4ec0b7:

Removed the "fixed in the Spec Kit framework" framing — the section now describes IV–VI as the typical customization focus areas while noting that /speckit.constitution lets teams define fewer or more principles than the template.
Collapsed Article V and VI into a single bullet that correctly reflects the template grouping them under one [PRINCIPLE_5_NAME] / [PRINCIPLE_5_DESCRIPTION] slot by default, with a note that teams can expand to separate articles via /speckit.constitution.
Reworded the /speckit.analyze sentence to say it validates all spec/plan artifacts against every principle in the project constitution, rather than implying article-number-specific logic.

Copilot

Copilot's findings

Files reviewed: 1/1 changed files
Comments generated: 2

+
+- **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 (example hint: *V. Observability, VI. Versioning & Breaking Changes*). Teams that need separate articles can expand to additional principle sections using `/speckit.constitution`.


+
+- **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 (example hint: *V. Observability, VI. Versioning & Breaking Changes*). Teams that need separate articles can expand to additional principle sections using `/speckit.constitution`.
+
+To define these articles, populate the corresponding principle sections in `.specify/memory/constitution.md` (generated from `templates/constitution-template.md`). The `/speckit.analyze` command validates all spec and plan artifacts against every principle in your project constitution, so any rules you define here are automatically applied during analysis.


mnriem · 2026-05-06T19:36:00Z

@copilot apply changes based on the comments in this thread

…erences Agent-Logs-Url: https://github.com/github/spec-kit/sessions/1c970cf3-767e-4e00-9e3b-db24461843e5 Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot · 2026-05-06T19:37:21Z

@copilot apply changes based on the comments in this thread

Applied both comments in b9c7a0c:

Updated the [PRINCIPLE_5_*] example hint to include "VII. Simplicity" so it exactly matches the template: V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity.
Updated the path reference to mention both locations: .specify/templates/constitution-template.md (in an initialized project) and templates/constitution-template.md (in the Spec Kit repo).

Copilot

Copilot's findings

Files reviewed: 1/1 changed files
Comments generated: 2

+
+- **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 (along with a Simplicity article) under a single `[PRINCIPLE_5_NAME]` / `[PRINCIPLE_5_DESCRIPTION]` slot (example hint: *V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity*). Teams that need separate articles can expand to additional principle sections using `/speckit.constitution`.


+
+- **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 (along with a Simplicity article) under a single `[PRINCIPLE_5_NAME]` / `[PRINCIPLE_5_DESCRIPTION]` slot (example hint: *V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity*). Teams that need separate articles can expand to additional principle sections using `/speckit.constitution`.
+
+To define these articles, populate the corresponding principle sections in `.specify/memory/constitution.md` (initialized from `.specify/templates/constitution-template.md` in your project, sourced from `templates/constitution-template.md` in the Spec Kit repo). The `/speckit.analyze` command validates all spec and plan artifacts against every principle in your project constitution, so any rules you define here are automatically applied during analysis.


mnriem · 2026-05-06T19:48:23Z

@copilot apply changes based on the comments in this thread

…ath notation Agent-Logs-Url: https://github.com/github/spec-kit/sessions/05743acb-4cf0-4c58-a67e-4b996b5e3088 Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot · 2026-05-06T19:51:18Z

@copilot apply changes based on the comments in this thread

Applied both comments in 88e9823:

Removed "along with a Simplicity article" and added a clarifying note that the [PRINCIPLE_5_*] example hint's label text is a suggestion only — teams can name and scope that slot however fits their project. This makes clear there's no conflict with the framework-provided "Articles VII & VIII" section below.
Standardized path notation to the short form memory/constitution.md (matching the existing convention at line 276), with the full .specify/memory/constitution.md path noted parenthetically for context.

Copilot

Copilot's findings

Files reviewed: 1/1 changed files
Comments generated: 1

mnriem · 2026-05-06T21:24:02Z

+
+- **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 (example hint: *V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity*). The label text is a suggestion only—teams can name and scope this slot however fits their project, or expand to separate articles using `/speckit.constitution`.
+
+To define these articles, populate the corresponding principle sections in `memory/constitution.md` (located at `.specify/memory/constitution.md` in your project, generated from `templates/constitution-template.md`). The `/speckit.analyze` command validates all spec and plan artifacts against every principle in your project constitution, so any rules you define here are automatically applied during analysis.


@copilot Fix this but keep in mind the /speckit.constitution command should be used to populate those aricles as they are project specific

Fixed in ad5d907. Replaced the template path reference with /speckit.constitution as the recommended way to define these project-specific articles, with .specify/memory/constitution.md noted as the file it populates.

Agent-Logs-Url: https://github.com/github/spec-kit/sessions/522bf148-2732-4ff2-9f3d-c3f92c9543f2 Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot

Copilot's findings

Files reviewed: 1/1 changed files
Comments generated: 2

+
+- **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 (example hint: *V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity*). The label text is a suggestion only—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 and plan artifacts against every principle in your project constitution, so any rules you define here are automatically applied during analysis.


+
+- **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 (example hint: *V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity*). The label text is a suggestion only—teams can name and scope this slot however fits their project, or expand to separate articles using `/speckit.constitution`.


mnriem · 2026-05-06T21:33:34Z

@copilot apply changes based on the comments in this thread

…analyze coverage Agent-Logs-Url: https://github.com/github/spec-kit/sessions/981ee0dc-5cef-444d-8cc2-1358e08825df Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot · 2026-05-06T21:35:13Z

@copilot apply changes based on the comments in this thread

Applied both in 32a90dd:

Removed the [PRINCIPLE_5_*] example hint entirely — the "(V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity)" text was causing the inconsistency by implying Article VII belongs to the customizable slot. The bullet now simply describes the slot as grouping Articles V & VI concerns by default, without anchoring to a specific example that conflicts with the separately-documented Articles VII & VIII section.
Updated the /speckit.analyze sentence to say "spec, plan, and task artifacts" to accurately reflect all three core artifacts the command covers.

Copilot

Copilot's findings

Files reviewed: 1/1 changed files
Comments generated: 2

+
+- **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.


+
+- **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`.


Initial plan

8112291

Copilot AI self-assigned this May 6, 2026

Copilot AI review requested due to automatic review settings May 6, 2026 13:51

Copilot AI assigned mnriem May 6, 2026

Copilot AI review requested due to automatic review settings May 6, 2026 13:51

Copilot started work on behalf of mnriem May 6, 2026 13:51 View session

Copilot AI linked an issue May 6, 2026 that may be closed by this pull request

docs: Document Articles IV, V, VI as project-customizable in spec-driven.md #2466

Open

docs: document Articles IV, V, VI as project-customizable in spec-dri…

7fe6448

…ven.md Agent-Logs-Url: https://github.com/github/spec-kit/sessions/a5a938bd-4400-4deb-bdc8-0109b0bf4ccb Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot AI requested review from Copilot and removed request for Copilot May 6, 2026 13:54

Copilot AI changed the title ~~[WIP] Document Articles IV, V, VI as project-customizable in spec-driven.md~~ docs: document Articles IV, V & VI as project-customizable in spec-driven.md May 6, 2026

Copilot AI requested a review from mnriem May 6, 2026 13:55

Copilot finished work on behalf of mnriem May 6, 2026 13:55

mnriem marked this pull request as ready for review May 6, 2026 16:38

mnriem requested review from Copilot and removed request for Copilot May 6, 2026 16:38

Copilot started reviewing on behalf of mnriem May 6, 2026 16:39 View session

mnriem requested review from Copilot and removed request for Copilot May 6, 2026 19:05

Copilot started reviewing on behalf of mnriem May 6, 2026 19:06 View session

Copilot AI reviewed May 6, 2026

View reviewed changes

Comment thread spec-driven.md Outdated

Comment thread spec-driven.md Outdated

Comment thread spec-driven.md Outdated

Copilot started work on behalf of mnriem May 6, 2026 19:22 View session

docs: fix Articles IV–VI section based on review feedback

d4ec0b7

Agent-Logs-Url: https://github.com/github/spec-kit/sessions/2501d2e9-fbcf-4d44-afe1-1fa19f1a0a24 Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot finished work on behalf of mnriem May 6, 2026 19:25

mnriem requested a review from Copilot May 6, 2026 19:29

Copilot started reviewing on behalf of mnriem May 6, 2026 19:30 View session

Copilot AI reviewed May 6, 2026

View reviewed changes

Copilot started work on behalf of mnriem May 6, 2026 19:36 View session

docs: fix PRINCIPLE_5 example hint and constitution template path ref…

b9c7a0c

…erences Agent-Logs-Url: https://github.com/github/spec-kit/sessions/1c970cf3-767e-4e00-9e3b-db24461843e5 Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot finished work on behalf of mnriem May 6, 2026 19:37

mnriem requested a review from Copilot May 6, 2026 19:39

Copilot started reviewing on behalf of mnriem May 6, 2026 19:40 View session

Copilot AI reviewed May 6, 2026

View reviewed changes

Copilot started work on behalf of mnriem May 6, 2026 19:48 View session

docs: reconcile PRINCIPLE_5 hint label and standardize constitution p…

88e9823

…ath notation Agent-Logs-Url: https://github.com/github/spec-kit/sessions/05743acb-4cf0-4c58-a67e-4b996b5e3088 Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot finished work on behalf of mnriem May 6, 2026 19:51

mnriem requested a review from Copilot May 6, 2026 21:17

Copilot started reviewing on behalf of mnriem May 6, 2026 21:17 View session

Copilot AI reviewed May 6, 2026

View reviewed changes

Copilot started work on behalf of mnriem May 6, 2026 21:24 View session

docs: point to /speckit.constitution for defining project articles IV-VI

ad5d907

Agent-Logs-Url: https://github.com/github/spec-kit/sessions/522bf148-2732-4ff2-9f3d-c3f92c9543f2 Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot finished work on behalf of mnriem May 6, 2026 21:26

mnriem requested a review from Copilot May 6, 2026 21:28

Copilot started reviewing on behalf of mnriem May 6, 2026 21:28 View session

Copilot AI reviewed May 6, 2026

View reviewed changes

Copilot started work on behalf of mnriem May 6, 2026 21:33 View session

docs: fix PRINCIPLE_5 example hint inconsistency and add tasks.md to …

32a90dd

…analyze coverage Agent-Logs-Url: https://github.com/github/spec-kit/sessions/981ee0dc-5cef-444d-8cc2-1358e08825df Co-authored-by: mnriem <15701806+mnriem@users.noreply.github.com>

Copilot finished work on behalf of mnriem May 6, 2026 21:35

mnriem requested a review from Copilot May 6, 2026 21:36

Copilot AI reviewed May 6, 2026

View reviewed changes


		- 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 (example hint: V. Observability, VI. Versioning & Breaking Changes). Teams that need separate articles can expand to additional principle sections using `/speckit.constitution`.


		- 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 (example hint: V. Observability, VI. Versioning & Breaking Changes). Teams that need separate articles can expand to additional principle sections using `/speckit.constitution`.

		To define these articles, populate the corresponding principle sections in `.specify/memory/constitution.md` (generated from `templates/constitution-template.md`). The `/speckit.analyze` command validates all spec and plan artifacts against every principle in your project constitution, so any rules you define here are automatically applied during analysis.


		- 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 (example hint: V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity). The label text is a suggestion only—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 and plan artifacts against every principle in your project constitution, so any rules you define here are automatically applied during analysis.

Conversation

Copilot AI commented May 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

Uh oh!

Uh oh!

Uh oh!

mnriem commented May 6, 2026

Uh oh!

Copilot AI commented May 6, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

mnriem commented May 6, 2026

Uh oh!

Copilot AI commented May 6, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

mnriem commented May 6, 2026

Uh oh!

Copilot AI commented May 6, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

mnriem May 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI May 6, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

mnriem commented May 6, 2026

Uh oh!

Copilot AI commented May 6, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented May 6, 2026 •

edited

Loading