speckit-constitution

Fill placeholder governance tokens into the Speckit constitution memory file.

1|Updated May 20, 2026
One-click install
npx skills add https://github.com/sabrydawood/claude-config --skill speckit-constitution-sabrydawood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/sabrydawood/claude-config/tree/main/skills/speckit-constitution
Command: npx skills add https://github.com/sabrydawood/claude-config --skill speckit-constitution-sabrydawood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It keeps your project governance document consistent and up to date by converting user-supplied principles into a fully populated, validated constitution.

Core Features & Use Cases

  • Interactive constitution drafting: Collects or derives concrete values for governance principles and placeholders.
  • Template-to-memory propagation: Fills .specify/memory/constitution.md from the constitution template and ensures dependent templates stay aligned.
  • Versioned governance changes: Applies semantic versioning for principle/section changes, updates amendment dates, and produces a change log.

Quick Start

Update your repository’s Speckit constitution by asking for the new principles and any governance rules you want the project to follow, then confirm the proposed version bump and overwrite the updated constitution in .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 a Speckit project constitution with new governance principles?

To update a Speckit project constitution, you provide new governance principles to the Skill, which fills the placeholder tokens in your `.specify/memory/constitution.md` file and synchronizes dependent templates. It then applies semantic versioning and propagates consistency across your project.

What is semantic versioning for project constitution governance changes?

Semantic versioning for project constitution governance tracks amendments by applying version bumps to principle changes, updating governance dates, and generating a change log. This ensures structured traceability when modifying your Speckit project constitution.

Does docs automation work with spec-kit template synchronization?

Yes, docs automation handles spec-kit template synchronization by filling the `.specify/memory/constitution.md` from the constitution template and ensuring dependent plan, spec, tasks, and command templates stay aligned without unresolved bracket tokens.

How do I validate that no unresolved bracket tokens remain in my constitution memory file?

You validate unresolved bracket tokens by running the consistency propagation workflow, which checks the populated `.specify/memory/constitution.md` file. This process ensures all governance placeholders are fully replaced with concrete values.

Can I specify different numbers of governance principles for my project constitution?

Yes, you can specify different numbers of principles for your project constitution. The Skill dynamically collects or derives concrete values for your governance principles, accommodating variable counts when populating the constitution memory file.

What is the best way to maintain consistency across plan, spec, and tasks templates?

The best way to maintain template consistency is using a constitution propagation workflow that synchronizes governance changes from `.specify/memory/constitution.md` across dependent plan, spec, tasks, and command templates while enforcing semantic versioning.