speckit-constitution

To update a project constitution, you convert provided principles into a validated, filled-in governance document. This process ensures correct placeholder replacement and updates versioning metadata like CONSTITUTION_VERSION and LAST_AMENDED_DATE before writing back to the constitution file.

Template consistency propagation is the process of checking related plan, spec, tasks, and command templates against an updated constitution. It records a Sync Impact Report and runs necessary template updates to ensure your repository's governance memory remains aligned.

To keep governance templates aligned in a Spec-Kit repository, you apply consistency checks before writing back to the memory directory. This ensures your constitution document remains synchronized with dependent plan, spec, tasks, and command templates.

Yes, the constitution update process handles governance versioning by validating and updating CONSTITUTION_VERSION, RATIFICATION_DATE, and LAST_AMENDED_DATE. If a ratification date is unavailable, it automatically marks the field as a TODO.

Yes, this approach supports hook-aware pre and post extension execution compatibility. The constitution update mechanism is designed to safely operate within environments that utilize pre and post execution hooks during template synchronization.

You should run a constitution synchronization check whenever you modify project principles. This ensures that all dependent templates are evaluated for impacts and updated if required, preventing structural drift across your governance documentation.