speckit-constitution

Update project constitutions and synchronize dependent templates in spec-kit projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the project's constitution current by collecting principle inputs, filling template tokens, enforcing versioning and date rules, and synchronizing dependent templates to prevent governance drift and inconsistent documentation.

Core Features & Use Cases

  • Template filling: Locate placeholder tokens in .specify/memory/constitution.md and replace them with user-provided or inferred values.
  • Governance versioning: Determine and increment CONSTITUTION_VERSION using semantic rules, set RATIFICATION_DATE and LAST_AMENDED_DATE appropriately.
  • Propagation & validation: Update related templates (plans, specs, tasks, and command docs), produce a Sync Impact Report, and flag manual follow-ups.
  • Use Case: During a governance update, use this Skill to apply principle changes, update templates across the repo, and generate a report for reviewers and CI checks.

Quick Start

Update the constitution by supplying principles or asking the skill to infer them from the repository and then apply and synchronize changes across templates.

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 project constitution and sync dependent templates?

To update a project constitution, you apply principle inputs to fill placeholder tokens in the constitution document, increment the semantic version, and propagate changes across all dependent plan, spec, and task templates to prevent documentation drift.

What is project constitution governance drift and how is it prevented?

Governance drift occurs when project principles change but dependent documentation does not. It is prevented by synchronizing template updates, enforcing semantic versioning, and generating a Sync Impact Report to flag manual follow-ups.

How does semantic versioning work for constitution documents?

Semantic versioning for a constitution involves determining and incrementing the CONSTITUTION_VERSION using semantic rules, while setting the RATIFICATION_DATE and LAST_AMENDED_DATE to appropriate ISO dates during updates.

Does this constitution sync process require a spec-kit structure?

Yes, the constitution sync process is designed for projects using the spec-kit structure, locating placeholder tokens within the .specify/memory/constitution.md file to fill and update.

What is included in a Sync Impact Report for template updates?

A Sync Impact Report includes the results of propagating constitution changes across related templates, preserving template integrity, and flagging specific manual follow-ups required for reviewers and CI checks.

Can I infer project principles automatically from an existing repository?

Yes, you can update the constitution by supplying principles directly or asking the skill to infer them from the existing repository, which then applies and synchronizes the changes across templates.