speckit-constitution

Updating a project constitution involves replacing template placeholders with new governance principles, propagating amendments across dependent plan and spec templates, applying semantic version bumps, and generating a Sync Impact Report to validate consistency before writing.

Template synchronization for project governance ensures that when constitution principles change, dependent plan, spec, and task templates automatically receive validated updates to remove outdated guidance and maintain structural consistency across the repository.

Applying semantic versioning to governance amendments requires incrementing the VERSION field, setting ISO-formatted governance dates, running consistency validation checks, and generating a Sync Impact Report before writing the updated constitution file.

No, the Speckit constitution amendment workflow does not require manual template updates. It automatically propagates amendments by validating and updating related templates and command references to remove outdated guidance during the constitution writing process.

To generate a Sync Impact Report for governance changes, you run the constitution update process with user-supplied or repo-inferred principles, which validates consistency and outputs the report for traceability before any files are actually written.

You need consistency validation for markdown frontmatter in project specifications when amending governance principles, ensuring that metadata fields, semantic version bumps, and ISO dates remain accurate and synchronized across all dependent templates.