speckit-constitution

Synchronize governance constitutions in .specify/memory/constitution.md with semantic versioning.

12|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/reason-healthcare/rh-skills --skill speckit-constitution-reason-healthcare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/reason-healthcare/rh-skills/tree/main/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/reason-healthcare/rh-skills --skill speckit-constitution-reason-healthcare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

Core Features & Use Cases

  • Load existing constitution, replace placeholders, and propagate governance changes across templates.
  • Maintain consistent versioning and ensure alignment with .specify/templates and tasks.
  • Synchronize related artifacts when principles are added or renamed.

Quick Start

Update the constitution by providing the desired principles or confirming prompts to apply changes to .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 automate updating project governance principles and sync them across templates?

To automate governance updates, this Skill applies user-provided principles to the .specify/memory/constitution.md file, replacing placeholders and propagating changes across related templates and tasks to keep everything synchronized.

What is a project constitution in software engineering documentation?

A project constitution is a foundational governance document defining core principles. This Skill manages the .specify/memory/constitution.md file, ensuring these principles are consistently versioned and aligned with dependent templates.

How do I use semantic versioning for governance constitution changes?

Semantic versioning records MAJOR, MINOR, or PATCH changes to the constitution. When you add or rename principles, the Skill automatically determines and applies the correct version bump to track governance modifications.

Do I need to manually update .specify/templates when renaming a constitution principle?

No, you do not need to manually update templates. Providing explicit inputs for renamed principles triggers automatic synchronization across .specify/templates and related tasks, maintaining alignment throughout the Spec kit.

Can I use this to create a new constitution from scratch?

Yes, you can create a new project constitution by providing desired principles through interactive prompts. The Skill replaces placeholders in the .specify/memory/constitution.md file and ensures dependent templates stay in sync.