speckit-constitution

To update a project constitution, this skill applies user inputs to the .specify/memory/constitution.md file and propagates amendments across dependent artifacts, ensuring governance metadata, timestamps, and versioning remain consistent throughout the repository.

Constitution versioning in spec-kit style repositories involves enforcing frontmatter constraints, computing version bumps, and synchronizing ratification dates and compliance checks across planning and task templates to maintain governance consistency.

You substitute placeholders in a project constitution markdown file by providing desired governance values interactively, which the skill then applies to refresh .specify/memory/constitution.md and align dependent artifacts.

Yes, this skill operates without external dependencies, relying solely on its internal logic to enforce frontmatter constraints, compute version bumps, and update dependent artifacts with consistent governance metadata.

The best way to maintain consistency is through automated template propagation, which synchronizes governance changes, version bumps, and placeholder substitutions across planning and task templates when the constitution is updated.

Frontmatter constraints fail when governance timestamps and version bumps are not enforced consistently during updates; this skill enforces these constraints and computes version bumps to ensure compliance across dependent artifacts.