speckit-constitution

Updating a project constitution involves converting interactive user inputs into a synchronized memory document. This process aligns your project's core principles with its templates, workflows, and governance artifacts automatically.

Constitution versioning in a spec-kit repository works by reading the existing constitution, applying your inputs, managing placeholders, and incrementing the version. It then propagates these governance updates across dependent project artifacts.

Project constitutions are synchronized memory artifacts that establish core principles to drive templates, workflows, and governance checks. You need to update them whenever you must align project governance with new or modified foundational principles.

Yes, you need a .specify directory to manage project governance and memory artifacts. This tool is specifically applicable to spec-kit repositories containing that directory, where it updates the constitution.md memory file.

Yes, you can automatically propagate constitution changes to dependent templates and documentation. The tool applies your input principles and propagates the updates across dependent templates, workflows, and governance artifacts.