speckit-constitution

Name: speckit-constitution
Availability: InStock
Author: imbatony

Update spec-kit constitution templates with inferred values and generate impact reports.

1|Updated Jun 16, 2025

Search Tags:#automation #template #versioning #constitution #governance #specify

Ready to run

npx skills add https://github.com/imbatony/pavone --skill speckit-constitution-imbatony

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/imbatony/pavone/tree/main/.claude/skills/speckit-constitution
Command: npx skills add https://github.com/imbatony/pavone --skill speckit-constitution-imbatony

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects using the spec‑kit framework often have a constitution template with placeholder tags that become outdated as principles evolve. Manually editing the file and keeping all related templates consistent is error‑prone and time‑consuming.

Core Features & Use Cases

Placeholder Resolution: Detects all [ALL_CAPS_IDENTIFIER] tags in .specify/memory/constitution.md and fills them using user input or inferred repository data.
Governance Versioning: Determines the appropriate semantic version bump (major, minor, patch) and updates ratification and amendment dates.
Consistency Propagation: Scans related spec‑kit templates (plan, spec, tasks, command files) to ensure they reflect the updated principles.
Impact Reporting: Generates an HTML‑comment summary of changes, required updates, and TODO items.

Quick Start

Request the skill to update the constitution with the new project name and any added principles.

Frequently Asked Questions about speckit-constitution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I update project constitution templates with placeholder tags automatically?▼

To update project constitution templates, the skill detects `[ALL_CAPS_IDENTIFIER]` tags in `.specify/memory/constitution.md` and fills them using user input or inferred repository data. It resolves placeholders to ensure your governance file reflects current principles.

How does semantic versioning work for spec-kit governance files?▼

Semantic versioning for spec-kit governance files determines the appropriate version bump (major, minor, or patch) based on principle changes. It automatically updates ratification and amendment dates when the constitution is modified.

Do I need a .specify directory to use this constitution versioning skill?▼

Yes, you need a `.specify` directory containing memory and template files. This skill is applied to spec-kit projects that already have this structure in place to read and update the constitution correctly.

Can I propagate governance changes across related spec-kit templates?▼

Yes, you can propagate governance changes across related spec-kit templates. The skill scans plan, spec, tasks, and command files to ensure they reflect the updated principles from your constitution automatically.

How do I track compliance impacts when amending a project constitution?▼

To track compliance impacts when amending a project constitution, the skill generates an HTML-comment summary. This impact report details applied changes, required updates, and TODO items across your spec-kit project.

What is the best way to keep spec-kit constitution files consistent without manual editing?▼

The best way to keep spec-kit constitution files consistent is using automated placeholder resolution, semantic version bumps, and consistency propagation across related templates. This eliminates error-prone manual edits.