What problem does it solve? Maintaining a consistent, versioned project constitution in a Spec Kit workflow requires manual template resolution, placeholder replacement, semantic version bumps, and governance validation, which is error-prone when done by hand. ## Core Features & Use Cases - Template Resolution: Runs the Spec Kit template resolver to compose the active constitution scaffold from project overrides, preset layers, and core fallbacks. - Semantic Versioning: Automatically increments the constitution version (MAJOR/MINOR/PATCH) based on the nature of governance changes and records ratification and amendment dates. - Sync Impact Report: Generates an HTML-comment report summarizing version changes, modified principles, added or removed sections, and deferred TODOs. - Extension Hooks: Executes optional and mandatory pre/post hooks declared in .specify/extensions.yml around the constitution update. - Use Case: A team adopting Spec Kit wants to codify engineering principles; invoke this Skill with the desired principles and it writes a validated, versioned constitution to .specify/memory/constitution.md. ## Quick Start Ask the agent to update the project constitution with your principles, for example: create a constitution with five principles covering code quality, testing, and security.