speckit-constitution

Propagate governance principle updates across Spec Kit constitution templates and memory.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/nalthoff/spec-kit-prep-specify --skill speckit-constitution-nalthoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/nalthoff/spec-kit-prep-specify/tree/main/.cursor/skills/speckit-constitution
Command: npx skills add https://github.com/nalthoff/spec-kit-prep-specify --skill speckit-constitution-nalthoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The constitution defines governance rules, principles, and versioning for a Spec Kit project, and keeps memory and templates in sync as inputs change.

Core Features & Use Cases

  • Propagates updates from interactive inputs to .specify/memory/constitution.md and related templates.
  • Validates and manages CONSTITUTION_VERSION (MAJOR/MINOR/PATCH) to maintain compatibility.
  • Supports both interactive prompts and scripted inputs for principle updates and removals.
  • Ensures governance dates (RATIFICATION_DATE, LAST_AMENDED_DATE) stay accurate and ISO-formatted.

Quick Start

Update governance principles and run a constitution sync to propagate changes.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema
How do I keep project governance principles in sync across memory and templates?

To keep governance principles in sync, you can propagate updates from interactive prompts or scripted inputs to the constitution file and related artifacts. This ensures memory, templates, and command references align when governance principles change.

How does constitution versioning work for managing compatibility in a project?

Constitution versioning manages compatibility using MAJOR, MINOR, and PATCH version identifiers. It validates and updates the CONSTITUTION_VERSION to maintain alignment across dependent artifacts when governance principles are modified.

Do I need a default constitution template before syncing governance principles?

Yes, you need a default constitution template located at .specify/memory/constitution.md before syncing. This file serves as the central repository for governance rules, principles, and versioning metadata required for cross-template consistency checks.

How do I update governance dates and keep them ISO-formatted when amending principles?

Governance dates are kept accurate and ISO-formatted by propagating changes during a constitution sync. The system ensures RATIFICATION_DATE and LAST_AMENDED_DATE fields are automatically validated and updated when governance principles are added or removed.

What's the best way to remove outdated governance principles from a Spec Kit project?

The best way to remove outdated governance principles is through interactive prompts or scripted inputs. The system propagates the removals across the constitution and dependent templates, maintaining cross-template consistency and updating the version policy.

Why does cross-template consistency fail after updating governance principles manually?

Cross-template consistency fails when manual updates bypass the constitution sync process. Running a constitution sync after principle changes validates the versioning policy and ensures governance rules are propagated correctly across all dependent artifacts.