speckit-constitution

Update constitution templates and increment version in spec-kit projects.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/daksh7011/immich-backup --skill speckit-constitution-daksh7011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/daksh7011/immich-backup/tree/main/.claude/skills/speckit-constitution
Command: npx skills add https://github.com/daksh7011/immich-backup --skill speckit-constitution-daksh7011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains and updates the project constitution to reflect user-provided principles, ensuring all dependent templates and governance artifacts stay in sync.

Core Features & Use Cases

  • Interactive constitution drafting and updates guided by user input.
  • Propagates changes across .specify/memory/constitution.md and dependent templates in the spec-kit project.
  • Validates placeholders, versioning, and amendment history to ensure governance integrity.

Quick Start

Run the interactive constitution wizard to update .specify/memory/constitution.md.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema
How do I update my project constitution and keep governance templates in sync?

To update your project constitution, run the interactive constitution wizard to modify .specify/memory/constitution.md. This automatically propagates placeholder changes across all dependent governance templates and emits a Sync Impact Report.

How does constitution versioning work in a spec-kit project?

Constitution versioning works by incrementing the CONSTITUTION_VERSION variable per semantic rules whenever .specify/memory/constitution.md is modified. This ensures governance integrity by tracking amendment history and validating placeholder updates.

Do I need a .specify directory structure to use automated constitution governance updates?

Yes, you need a .specify directory structure containing constitution templates and memory files. The constitution updater applies specifically to spec-kit projects, modifying .specify/memory/constitution.md to align governance artifacts with principle inputs.

What is the best way to draft and propagate project principles across governance artifacts?

The best way to draft project principles is through interactive inputs that update .specify/memory/constitution.md. Changes are then automatically propagated across dependent templates, replacing placeholders to keep all governance artifacts aligned.

Why are my constitution placeholders not updating correctly across spec-kit templates?

Constitution placeholders may not update correctly if the .specify/memory/constitution.md file structure is invalid or if versioning rules are violated. The updater validates placeholders and amendment history to ensure governance integrity before propagating changes.