speckit-constitution

You can synchronize project governance principles by updating the constitution file, which automatically propagates the new principles to all dependent templates, plans, and commands. A Sync Impact Report is generated to summarize the changes made across the repository.

Semantic versioning for a project constitution increments the version number based on the significance of the governance changes applied. When user-provided principles are synced into the constitution file, the version is automatically updated following standard semantic versioning rules.

Yes, the constitution update flow can gather values directly from repository context rather than requiring manual input. It identifies placeholders and derives principles from existing repository data to populate the constitution automatically.

The best way to ensure templates reflect governance changes is to use an automated sync flow that validates and propagates updates. This process updates related tasks, plans, commands, and guidance docs to maintain consistency with the new constitution principles.

To update a constitution without breaking consistency, the system applies an update flow that identifies placeholders, gathers values, and ensures all related templates and guidance docs reflect the new principles. It validates changes and generates a Sync Impact Report.

Yes, constitution synchronization targets a specific repository path. The system updates the constitution file located within the repository's .specify/memory/ directory to ensure all dependent artifacts stay in sync with the latest governance principles.