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 increments 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 and Extension Hooks: Separates governance content from unrelated implementation requests and executes pre/post hooks declared in .specify/extensions.yml. - Use Case: A team adopting spec-kit wants to codify five engineering principles. Invoke the Skill with the principle list, and it produces a validated, versioned constitution with a suggested commit message. ## Quick Start Ask the agent to update the project constitution with your list of principles, for example by saying: create a constitution with principles for code quality, testing, and documentation.
