speckit-constitution

To keep your project constitution and spec templates in sync, you can use a tokenized template filling process that propagates governance changes across plan, spec, tasks, and command templates while ensuring consistent versioning and amendment metadata.

A tokenized project constitution template is a structured document containing placeholders for principle values. It gets updated into a concrete governance document by collecting user-provided or inferred inputs and filling the required placeholders.

You can execute pre and post-update hooks for spec-kit governance updates by defining optional or mandatory extension behaviors in your .specify/extensions.yml file, which orchestrates the hook execution during the constitution update process.

Yes, you can update your spec-kit constitution using inferred inputs. The update process respects user-provided values but will automatically infer missing principle values to ensure the governance document is fully populated.

Yes, spec-kit constitution propagation applies to command templates. When updating your project constitution, the process coordinates updates across plan, spec, tasks templates, and related command templates to maintain consistency.

To format dates and versioning metadata in a project constitution, the update process applies consistent versioning, amendment metadata, and date formatting rules automatically when generating the concrete governance document from your principles.