speckit.constitution

Create or update the project constitution and propagate changes across dependent templates.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/hduoc2003/leviathan-guardian --skill speckit-constitution-hduoc2003
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit.constitution
Source: https://github.com/hduoc2003/leviathan-guardian/tree/main/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/hduoc2003/leviathan-guardian --skill speckit-constitution-hduoc2003

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a project constitution in sync with dependent specification, plan, and task templates is error-prone manual work; this Skill fills the constitution template, versions it correctly, and propagates amendments across 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 rules (MAJOR/MINOR/PATCH). - Consistency Propagation: Validates and updates plan, spec, tasks, and command templates so they stay aligned with amended principles. - Sync Impact Report: Prepends an HTML comment report listing version changes, modified principles, and templates requiring follow-up. - Use Case: After adopting a new testing-discipline principle, run this Skill to amend the constitution to a new minor version and automatically flag every template that references the old governance rules. ## Quick Start Update the project constitution to add a new principle requiring integration tests for all public APIs and sync the 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 update a project constitution with spec-kit?▼

Provide your principle changes as input, and the Skill fills the constitution template at `.specify/memory/constitution.md`, bumps the version per semantic rules, and propagates amendments to dependent templates. It finishes with a summary and suggested commit message.

How is constitution versioning decided?▼

Versioning follows semantic rules: MAJOR for backward-incompatible principle removals or redefinitions, MINOR for new principles or expanded guidance, and PATCH for clarifications or wording fixes. If the bump type is ambiguous, the Skill proposes reasoning before finalizing.

Does it update dependent spec and plan templates automatically?▼

Yes, it reads plan-template.md, spec-template.md, tasks-template.md, and command files under `.specify/templates/` to verify alignment with updated principles, then records each as updated or pending in the Sync Impact Report.

What happens if the ratification date or other values are unknown?▼

The Skill inserts a `TODO(<FIELD_NAME>)` placeholder with an explanation and lists it under deferred items in the Sync Impact Report, so no placeholder is left unexplained.

Can I update only one principle without rewriting everything?▼

Yes, partial updates are supported. The Skill still runs full validation, version decision, and template consistency checks even when only a single principle is revised.