speckit-constitution

Create or update the project constitution and sync dependent spec-kit templates.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/gkuga/monit-rs --skill speckit-constitution-gkuga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/gkuga/monit-rs/tree/main/.claude/skills/speckit-constitution
Command: npx skills add https://github.com/gkuga/monit-rs --skill speckit-constitution-gkuga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a project's governing principles consistent across a spec-kit repository is tedious: the constitution file contains placeholder tokens, and every change must be propagated to plan, spec, and task templates. This Skill fills the constitution template with concrete values and keeps all dependent artifacts aligned. ## Core Features & Use Cases - Constitution Authoring: Replaces placeholder tokens in .specify/memory/constitution.md with values from user input or repository context. - Semantic Versioning: Automatically bumps the constitution version (MAJOR/MINOR/PATCH) based on the nature of governance changes. - Consistency Propagation: Validates and updates plan, spec, tasks, and command templates against the amended principles, then emits a Sync Impact Report. - Use Case: After deciding to add a new testing-discipline principle, run this Skill to amend the constitution, bump the minor version, and flag which templates need matching updates. ## Quick Start Update the project constitution to add a principle requiring integration tests for every new feature and sync all dependent templates.

Frequently Asked Questions about speckit-constitution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a project constitution with spec-kit?

Run the constitution command with your principles as input. The Skill loads `.specify/memory/constitution.md`, replaces every bracketed placeholder with concrete values, and writes the completed file back with proper versioning.

How does constitution versioning work in spec-kit?

The constitution follows semantic versioning: MAJOR for backward-incompatible principle removals, MINOR for new principles or sections, and PATCH for clarifications. The Skill proposes a bump type with reasoning before finalizing.

What happens if the constitution file is missing?

If `.specify/memory/constitution.md` does not exist, the Skill copies it from `.specify/templates/constitution-template.md` first, then proceeds with filling placeholders and validation.

Does updating the constitution sync other spec-kit templates?

Yes. The Skill reads plan-template.md, spec-template.md, tasks-template.md, and command files to verify alignment with amended principles, then reports each template as updated or pending in a Sync Impact Report.

What if required constitution information is unknown?

When critical data like the ratification date is unavailable, the Skill inserts a `TODO(<FIELD_NAME>)` marker with an explanation and lists it under deferred items in the Sync Impact Report.