What problem does it solve? Keeping a project's governing principles consistent across a spec-kit project is tedious: the constitution file, plan templates, spec templates, and task templates all drift out of sync when principles change. This Skill fills the constitution template with concrete values and propagates amendments across all dependent artifacts. ## Core Features & Use Cases - Constitution Authoring: Fills placeholder tokens in .specify/memory/constitution.md from user input or repository context, with semantic version bumping (MAJOR/MINOR/PATCH) based on the nature of changes. - Consistency Propagation: Validates and updates plan, spec, tasks, and command templates so they align with new or removed principles. - Sync Impact Report: Prepends an HTML comment summarizing version changes, modified principles, and templates requiring follow-up. - Extension Hooks: Executes optional or mandatory pre/post hooks declared in .specify/extensions.yml. - Use Case: A team adopting spec-kit wants to codify five engineering principles (e.g., test discipline, observability) and have every downstream template reflect them automatically. ## Quick Start Ask the assistant to create or update the project constitution with your principles, for example: "Update the project constitution to add an observability principle and bump the version."
