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

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>

Author: Copilot

spec-driven.md

@@ -326,7 +326,7 @@ Articles IV, V, and VI are the primary areas the constitution template reserves
 
 - **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.
+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.
 
 #### Articles VII & VIII: Simplicity and Anti-Abstraction