What problem does it solve? Teams using spec-driven development need a single, versioned governance document that defines non-negotiable engineering principles, but drafting and maintaining a constitution with consistent versioning, dates, and structure is error-prone manual work. ## Core Features & Use Cases - Constitution Authoring: Resolves the active constitution template and fills every placeholder with values from user input or repository context. - Semantic Versioning of Governance: Automatically bumps the constitution version using MAJOR/MINOR/PATCH rules based on the nature of the amendment. - Sync Impact Reporting: Produces an HTML-comment report listing version changes, modified principles, and deferred TODOs for human review. - Use Case: A team lead runs the command with principles like "code review required" and "test coverage mandatory" to generate .specify/memory/constitution.md v1.0.0 that all later spec-kit commands read at runtime. ## Quick Start Ask the assistant to create a project constitution with principles for code review, testing, and documentation using the speckit-constitution skill.