Skip to content

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

Open
Copilot wants to merge 13 commits intomainfrom
copilot/docs-spec-driven-update-articles-iv-v-vi
Open

docs: document Articles IV, V & VI as project-customizable in spec-driven.md#2467
Copilot wants to merge 13 commits intomainfrom
copilot/docs-spec-driven-update-articles-iv-v-vi

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 6, 2026

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-Specific Standards between Article III and Articles VII & VIII:
    • Identifies each article's typical domain: IV → integration concerns, V → operational concerns, VI → lifecycle concerns
    • Notes these are reserved for project-specific standards that teams define to suit their needs
    • Describes the articles in generic terms without referencing template internals or other files

Copilot AI self-assigned this May 6, 2026
Copilot AI review requested due to automatic review settings May 6, 2026 13:51
Copilot AI review requested due to automatic review settings May 6, 2026 13:51
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 mnriem marked this pull request as ready for review May 6, 2026 16:38
@mnriem mnriem requested review from Copilot and removed request for Copilot May 6, 2026 16:38
@mnriem mnriem requested review from Copilot and removed request for Copilot May 6, 2026 19:05
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

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

Comment thread spec-driven.md Outdated
Comment thread spec-driven.md Outdated
Comment thread spec-driven.md Outdated
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented May 6, 2026

@copilot apply changes based on the comments in this thread

Copy link
Copy Markdown
Contributor Author

Copilot AI commented May 6, 2026

@copilot apply changes based on the comments in this thread

Applied all three review comments in d4ec0b7:

  1. 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.
  2. 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.
  3. 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.

Remove references to template placeholders, file paths, and commands.
Describe each article's typical focus area in generic terms without
referencing anything outside spec-driven.md itself.
@mnriem mnriem requested a review from Copilot May 7, 2026 12:58
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

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

Comment thread spec-driven.md Outdated
Comment thread spec-driven.md Outdated
@mnriem
Copy link
Copy Markdown
Collaborator

mnriem commented May 7, 2026

@copilot apply changes based on the comments in this thread

Copy link
Copy Markdown
Contributor Author

Copilot AI commented May 7, 2026

@copilot apply changes based on the comments in this thread

Applied both in 5c64bbf:

  1. Broadened the intro phrase to "domain, operational, and lifecycle needs" so it covers all three article types (IV, V, and VI).
  2. Fixed the grammar to "however fits their project best".

Copilot finished work on behalf of mnriem May 7, 2026 16:31
Copilot AI requested a review from mnriem May 7, 2026 16:31
@mnriem mnriem requested a review from Copilot May 7, 2026 17:32
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

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

Comment thread spec-driven.md Outdated
Comment thread spec-driven.md Outdated
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings May 7, 2026 17:36
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

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

Comment thread spec-driven.md Outdated

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

Articles IV, V, and VI are reserved for project-specific standards that teams define to suit their domain, operational, and lifecycle needs:
Comment thread spec-driven.md Outdated
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings May 7, 2026 18:25
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

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

Comment thread spec-driven.md Outdated
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings May 7, 2026 18:40
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

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

Comment thread spec-driven.md Outdated
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings May 8, 2026 19:07
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot's findings

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

Comment thread spec-driven.md
Comment on lines +321 to +322
#### Project-Specific Standards: Common Constitution Areas

Comment thread spec-driven.md

#### Project-Specific Standards: Common Constitution Areas

Project-specific standards are defined by each team in their constitution via `/speckit.constitution`. A project may define fewer or more principles than any default template, but in many constitutions these standards often cover areas such as integration, operations, and lifecycle expectations:
Comment thread spec-driven.md

- **Article VI** may address lifecycle concerns—such as versioning schemes, breaking-change policies, or deprecation strategies.

These article numbers are illustrative rather than reserved slots. Teams are free to define, name, scope, add, remove, or reorder principles in whatever way best fits their project, with `/speckit.constitution` serving as the mechanism for codifying those project-specific architectural standards.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

3 participants