speckit-constitution

A project constitution defines and enforces formal principles to govern specifications, plans, and implementations. It prevents drift by categorizing rules as MUST or SHOULD, validating consistency, and synchronizing templates across repositories.

You create a project constitution by running the constitution tool to interactively gather and categorize principles. It then synchronizes dependent templates, such as spec, plan, task, and checklist templates, to enforce constraints across repositories.

Template synchronization applies your project constitution to dependent spec, plan, task, and checklist templates. It enforces constraints by validating consistency and reporting changes, maintaining alignment between memory and orchestration layers.

You need formal governance principles when you experience drift and misalignment across specifications and implementations. A project constitution prevents this by establishing formal standards that validate consistency across your knowledge base.

Yes, you can validate consistency and report changes across the knowledge base. The constitution tool synchronizes dependent templates and applies constraints to maintain alignment between memory and orchestration layers.

The best way to maintain alignment is to define and enforce a project constitution. It applies constraints across repositories to validate principles and synchronize dependent templates, preventing orchestration drift.