What problem does it solve? Teams using spec-kit workflows need a single authoritative rule layer for principles and governance before specification, planning, and task work can proceed consistently. This Skill creates or updates .specify/memory/constitution.md with proper semantic versioning, placeholder resolution, and downstream impact reporting. ## Core Features & Use Cases - Constitution Authoring: Creates or revises the project constitution with concrete principles, governance metadata, and semantic version bumps (MAJOR/MINOR/PATCH). - Sync Impact Report: Prepends a report listing modified principles, pending template/doc follow-ups, and the exact downstream re-entry path (/sp-specify, /sp-plan, /sp-tasks, or /sp-analyze). - Strict Write Boundary: Writes only the constitution file, treating templates, workflow state, and project cognition artifacts as read-only context. - Use Case: A team adopting spec-kit runs this Skill to replace placeholder tokens in their constitution with real principles, then receives a report flagging which templates and active feature artifacts need alignment. ## Quick Start Ask the agent to update the project constitution with your team's core engineering principles and governance rules.