What problem does it solve? Teams using spec-kit projects need a single source of truth for code quality standards, testing requirements, and architectural constraints, but drafting and maintaining a constitution document with consistent versioning and cross-template alignment is tedious and error-prone. ## Core Features & Use Cases - Template Filling: Replaces placeholder tokens in .specify/memory/constitution.md with concrete values derived from user input or repository context. - Semantic Versioning: Automatically increments the constitution version (MAJOR/MINOR/PATCH) based on the nature of governance changes. - Consistency Propagation: Validates that plan, spec, tasks, and command templates stay aligned with updated principles, and produces a Sync Impact Report. - Use Case: At the start of a new spec-kit project, run this Skill to establish five core principles (e.g., test-first development, documentation requirements) and propagate them across all project templates. ## Quick Start Ask the agent to create or update the project constitution with your desired principles, for example: "Update the project constitution to add a principle requiring integration tests for all API endpoints."
