speckit-constitution

Update constitution files by resolving placeholders and applying semantic versioning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates creating and updating the repository's constitution file at .specify/memory/constitution.md by collecting principle inputs, resolving template placeholders, and ensuring dependent templates and command files stay in sync. It reduces manual edits, prevents governance drift, and enforces consistent versioning and amendment records across the repo.

Core Features & Use Cases

  • Placeholder resolution: Identifies tokens of the form [ALL_CAPS_IDENTIFIER] in the constitution template and fills them from user input or inferred repository context.
  • Versioning & governance: Applies semantic version increments (major/minor/patch), manages RATIFICATION_DATE and LAST_AMENDED_DATE, and produces a Sync Impact Report summarizing changes.
  • Template synchronization: Validates and updates related templates (.specify/templates/plan-template.md, spec-template.md, tasks-template.md) and command files, flagging files that require manual follow-up.
  • Use Case: When project principles change, run this Skill to update the constitution, increment the version appropriately, export a Sync Impact Report, and prepare a suggested commit message.

Quick Start

Update the project's constitution using provided principles or interactive prompts and produce a Sync Impact Report.

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 to keep governance documents in sync?

Syncing project templates involves validating and updating dependent files like plan-template.md, spec-template.md, and tasks-template.md alongside the constitution. This Skill flags any template synchronization issues requiring manual follow-up and produces a Sync Impact Report summarizing the detected changes.

How does semantic versioning work when amending a repository constitution?

Managing placeholder tokens requires resolving [ALL_CAPS_IDENTIFIER] patterns within the constitution template from user input or inferred repository context. This Skill automates identifying and replacing these bracketed placeholders to ensure governance documents are populated consistently without manual edits.

Does this constitution update tool require a specific repository directory structure?

Yes, updating the constitution requires a spec-kit repository structure containing a .specify directory. This directory must include specific subdirectories for templates, memory, and commands to enable proper placeholder resolution, file writing, and consistency checks across governance files.

What is the best way to prevent governance drift when changing project principles?

Preventing governance drift is achieved by running an automated consistency check across templates and command files after updating the constitution. This Skill validates that dependent governance files remain synchronized with the new principles, flagging any mismatches that require manual follow-up in a Sync Impact Report.