speckit-constitution

To automatically sync your project constitution, you provide interactive principle inputs or run with defaults to update `.specify/memory/constitution.md` and align it with `.specify/templates/constitution-template.md`. This ensures governance templates stay synchronized without manual file edits.

A project constitution defines core governance principles for your codebase. You need to initialize governance templates when establishing a `.specify` directory to ensure standardized versioning, ratification tracking, and principle alignment across your project from the start.

You derive and update governance principles by supplying interactive inputs to the system, which then processes your supplied principles against existing templates to automatically generate or update the project constitution while maintaining semantic versioning rules.

Yes, constitution template synchronization supports semantic versioning by tracking ratification and amendment dates within the `.specify` directory structure. This ensures all governance document updates are properly versioned and historically logged.

Yes, you can use optional extensions for pre-execution hooks when updating your project constitution. These hooks integrate into the `.specify` directory workflow to trigger custom automated actions before constitution derivation or template synchronization processes run.

Governance documents fall out of sync when `.specify/memory/constitution.md` is edited manually without updating `.specify/templates/constitution-template.md`. Using automated constitution derivation prevents this drift by synchronizing both files simultaneously from your principle inputs.