From 3cfc81ff316b3ccdca2aa80500b300787d20212e Mon Sep 17 00:00:00 2001 From: YNan_varamor <270133796@163.com> Date: Tue, 23 Jun 2026 22:57:26 +0930 Subject: [PATCH] docs: clarify project-defined constitution articles (#2994) Co-authored-by: yann lei --- spec-driven.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/spec-driven.md b/spec-driven.md index 090071a3c..28259ae28 100644 --- a/spec-driven.md +++ b/spec-driven.md @@ -318,6 +318,12 @@ 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-Defined Governance + +Articles IV, V, and VI are intentionally defined by each project's constitution rather than prescribed by Spec Kit. The constitution template provides placeholder slots and example concerns such as integration testing, observability, versioning, and breaking changes, but teams replace those placeholders with the principles that match their system and organization. + +This keeps the nine-article structure stable while allowing each project to encode its own non-negotiable standards. For one project, Article IV might govern security and access boundaries; for another, it might define integration test requirements. The `/speckit.analyze` command evaluates the concrete constitution in the project, so these project-defined articles participate in compliance checks just like the built-in examples. + #### Articles VII & VIII: Simplicity and Anti-Abstraction These paired articles combat over-engineering: