speckit-constitution

Automate constitution creation and updates from principle inputs for .specify projects.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/apply-the/canon --skill speckit-constitution-apply-the
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/apply-the/canon/tree/main/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/apply-the/canon --skill speckit-constitution-apply-the

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual governance updates are error-prone and hard to keep in sync across templates and artifacts. speckit-constitution automates creating or updating the project constitution from interactive or provided principle inputs, ensuring consistency.

Core Features & Use Cases

  • Automates constitution drafting and syncing across .specify templates.
  • Propagates amendments to dependent artifacts and templates to maintain governance integrity.
  • Supports interactive inputs and batch principle updates, with version tracking.

Quick Start

Initialize constitution alignment by running the speckit-constitution workflow against your repository's .specify setup to refresh .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 project constitution updates across .specify templates?

Automating project constitution updates involves applying interactive or batch principle inputs to populate .specify templates, propagating amendments to dependent artifacts, and incrementing CONSTITUTION_VERSION to maintain governance sync.

What is the best way to keep governance artifacts in sync with a project constitution?

Keeping governance artifacts in sync requires propagating constitution amendments to dependent templates, generating a Sync Impact Report, and recording RATIFICATION_DATE and LAST_AMENDED_DATE to track governance changes accurately.

How does constitution versioning work in spec-kit projects?

Constitution versioning in spec-kit projects works by incrementing CONSTITUTION_VERSION, recording RATIFICATION_DATE and LAST_AMENDED_DATE, and overwriting the .specify/memory/constitution.md file to ensure governance consistency across templates.

Do I need an existing .specify/memory/constitution.md file to synchronize project governance?

Yes, synchronizing project governance requires an existing .specify/memory/constitution.md file to update placeholders, apply amendments, and keep dependent artifacts in sync with the latest constitution version.

Can I update multiple governance principles at once in a project constitution?

Yes, you can update multiple governance principles at once by providing batch principle inputs, which the workflow applies to populate the constitution, propagate amendments, and generate a Sync Impact Report.

What limitations exist when automating constitution updates with spec-kit?

Automating constitution updates is limited to spec-kit projects using .specify templates, requires an existing .specify/memory/constitution.md file, and overwrites the constitution file during the synchronization process.