What problem does it solve? Teams using spec-driven development need a single, versioned governance document that defines project principles, but drafting and maintaining a constitution manually is error-prone and inconsistent. This Skill fills the constitution template at .specify/memory/constitution.md with concrete values, enforces semantic versioning, and keeps governance changes auditable. ## Core Features & Use Cases - Template-Driven Constitution Updates: Loads the existing constitution template, identifies every placeholder token, and replaces it with values derived from user input or repository context. - Semantic Versioning of Governance: Automatically bumps the constitution version using MAJOR/MINOR/PATCH rules and records ratification and amendment dates in ISO format. - Sync Impact Report: Prepends an HTML comment summarizing version changes, modified principles, added or removed sections, and deferred TODOs. - Scope Guard & Extension Hooks: Rejects non-governance requests (deferring them to other Spec Kit commands) and executes optional or mandatory pre/post hooks defined in .specify/extensions.yml. - Use Case: A team adopting Spec Kit runs the constitution command with principles like "code review required" and "test coverage mandatory" to produce a ratified, versioned governance document that all later spec, plan, and task commands reference. ## Quick Start Ask the assistant to create or update the project constitution with your chosen principles, for example by requesting a constitution with three principles covering code quality, testing, and documentation.
