speckit-constitution

To update a Spec Kit constitution, provide your governance principles as input. The system replaces template placeholders with concrete text, applies semantic version bumping, and writes the finalized principles to the project's constitution memory file.

Spec Kit constitution synchronization detects and executes pre-constitution hooks defined in .specify/extensions.yml before updating, and triggers after-constitution hooks once the file write is complete, ensuring custom extension logic integrates cleanly.

Yes, governance changes propagate automatically. The system validates and updates dependent Spec Kit templates, including plan, spec, tasks, and command markdown files, to ensure principle modifications remain strictly aligned across the project.

If the constitution memory file is missing, the update process handles the initialization automatically. It establishes the required constitution memory structure before applying deterministic template token replacement and writing the new principles.

To prevent stale templates after a principle update, run a consistency propagation check. This process verifies and updates related Spec Kit templates and command markdown files, enforcing deterministic token replacement and correct principle count handling.

Yes, Spec Kit applies semantic version bumping and enforces date rules during the constitution update. This ensures governance documents maintain accurate historical tracking and compliance alongside synchronized template updates.