What problem does it solve? Keeping a project's governing principles consistent across a spec-kit workflow is tedious: the constitution file, plan/spec/tasks templates, and command files can drift out of sync when principles change. This Skill fills the constitution template with concrete values, versions it semantically, and propagates amendments to all dependent artifacts. ## Core Features & Use Cases - Constitution authoring: Fills every placeholder token in .specify/memory/constitution.md from user input or repository context, with semantic version bumping (MAJOR/MINOR/PATCH) and ISO dates. - Consistency propagation: Validates and updates plan, spec, tasks, and command templates so they reflect new or removed principles, then prepends a Sync Impact Report to the constitution. - Extension hooks: Executes optional or mandatory before/after hooks declared in .specify/extensions.yml. - Use Case: After deciding to add a new testing-discipline principle, run this Skill to amend the constitution to a new minor version and automatically flag which templates need matching updates. ## Quick Start Ask the assistant to update the project constitution with your principles, for example: "Update the project constitution to add a principle requiring integration tests for all public APIs."