speckit-constitution

You can automate project constitution updates by providing interactive inputs or governance principles, which the system uses to fill .specify/memory/constitution.md and synchronize dependent artifacts. It handles placeholder replacement for variables like [PROJECT_NAME] and ensures all templates stay in sync.

Placeholder propagation works by deriving values from your updated constitution inputs and replacing variables like [PROJECT_NAME] across all dependent artifacts. When constraints change, the system automatically synchronizes these updates to ensure governance alignment throughout your templates.

Yes, you need an existing constitution template to use automated governance synchronization. The system requires a base .specify/memory/constitution.md file and ISO-8601 formatted dates to properly handle versioning policies and propagate updates to dependent artifacts.

You can track governance versioning and amendment rationale by updating your constitution with new principle inputs. The system documents the changes, applies versioning policies, and records the rationale for each amendment across all synchronized templates.

The best way to keep dependent artifacts in sync is to update your constitution through the automated system, which propagates placeholder changes and governance updates across all .specify templates simultaneously. This ensures versioning policies and constraints remain aligned without manual intervention.

Constitution template updates fail without valid ISO-8601 dates because the versioning policy and amendment tracking require standardized date formats. You must provide ISO-8601 formatted dates to ensure proper governance synchronization and placeholder replacement across dependent artifacts.