speckit-constitution

To create or update a project constitution, you supply interactive or provided principle inputs covering governance and rules. The system merges these with existing content, preserves history, and applies semver versioning to keep governance aligned.

Template synchronization for project governance ensures dependent templates like plan, spec, and tasks stay aligned with the constitution. It derives placeholder values from the constitution and updates dependent documents to reflect current principles.

Constitution versioning works by incrementing the CONSTITUTION_VERSION semver in the .specify/memory/constitution.md file. This tracks governance changes over time and triggers a Sync Impact Report detailing affected templates and recommended follow-ups.

Yes, you can use interactive inputs to modify your project constitution. The system accepts interactive or provided principle inputs, merges them with existing governance rules, and updates the .specify/memory/constitution.md file accordingly.

A Sync Impact Report is generated after updating a project constitution to detail changed sections, affected templates, and recommended follow-ups. You need it when modifying governance principles to understand downstream documentation impacts.

The best way to keep plan, spec, and tasks templates aligned is running a constitution sync. This process reads modified governance principles, derives placeholder values, and applies template synchronization across all dependent project documents.