speckit-constitution

Automate project constitution updates by deriving placeholder values from user input and repository context, then propagating versioned changes across dependent governance documents and templates. It replaces placeholder tokens with concrete values and generates a Sync Impact Report to track synchronization.

Semantic versioning for governance documents enforces MAJOR, MINOR, and PATCH version increments based on the scope of constitutional changes. The system applies the correct version bump automatically during the update workflow and propagates the new version across all dependent artifacts.

Syncing placeholders in a project constitution involves extracting concrete values from repository context and user input to fill template tokens. The workflow coordinates placeholder replacement across governance artifacts, ensuring all dependent documents reflect the updated project values accurately.

Existing templates and governance documents are required for the constitution sync workflow to function properly. The system applies derived values, increments versions, and propagates updates across these dependent artifacts, generating a Sync Impact Report to verify successful synchronization across your project.

A project constitution version fails to increment when the update workflow does not detect valid governance changes or lacks sufficient repository context. Ensure user input provides the necessary values for placeholder replacement so the system can enforce the appropriate MAJOR, MINOR, or PATCH version bump.

A constitution sync workflow operates without external dependencies, relying solely on repository context and user input to update project management governance documents. It derives values, replaces placeholder tokens, and propagates semantic version increments across templates independently.