speckit-constitution

Update project constitutions by filling placeholders and propagating changes across templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams maintain a living project constitution by deriving concrete values for placeholders and updating the central memory document at .specify/memory/constitution.md, ensuring all dependent templates stay in sync.

Core Features & Use Cases

  • Load and interpret the existing constitution, extract placeholders, and derive values from repository context or explicit user input.
  • Update the constitution memory and governance sections, propagate amendments across dependent artifacts, and align versioning with semantic rules.
  • Validate consistency with governance templates and related plan/specification artifacts, and generate a Sync Impact Report for traceability.

Quick Start

Run the speckit-constitution skill to refresh the constitution and 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 automate updating placeholders in a spec-kit project constitution?

It automates project constitution updates by deriving values for placeholders like [RATIFICATION_DATE] and [LAST_AMENDED_DATE] from repository context or explicit input. The skill updates the central memory document and propagates amendments across dependent templates while aligning versioning with semantic rules.

What is the best way to keep governance templates synchronized with a project constitution?

The best way to keep governance templates synchronized is using an automated constitution sync skill. It propagates changes across dependent artifacts, validates consistency with governance templates, and generates a Sync Impact Report for traceability across plan/spec/templates.

How does semantic versioning work when amending a project constitution?

Semantic versioning for a project constitution amendment aligns with MAJOR/MINOR/PATCH rules. The skill automatically applies these versioning requirements when updating the constitution memory, ensuring version numbers reflect the scale of changes propagated across templates and artifacts.

Can I use spec-kit constitution automation with my existing .specify directory structure?

Yes, spec-kit constitution automation works with existing .specify directory structures. It loads and interprets the current constitution from .specify/memory/constitution.md, extracts placeholders, and updates governance sections while validating consistency against related plan and specification artifacts.

Why do my project constitution placeholders remain empty after template changes?

Constitution placeholders remain empty when updates are not propagated across all dependent artifacts. The skill solves this by extracting placeholders, deriving concrete values, and cross-checking consistency against plan/spec/templates to ensure all governance documents stay in sync.