speckit-constitution

Create or update the project constitution and sync dependent spec-kit templates.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill speckit-constitution-sethdavis512
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/sethdavis512/iridium/tree/main/.claude/skills/speckit-constitution
Command: npx skills add https://github.com/sethdavis512/iridium --skill speckit-constitution-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a project's governing principles consistent across a spec-kit workflow is tedious: the constitution file, plan/spec/tasks templates, and command files can drift out of sync when principles change. This Skill fills the constitution template with concrete values, versions it semantically, and propagates amendments to all dependent artifacts. ## Core Features & Use Cases - Constitution authoring: Fills every placeholder token in .specify/memory/constitution.md from user input or repository context, with semantic version bumping (MAJOR/MINOR/PATCH) and ISO dates. - Consistency propagation: Validates and updates plan, spec, tasks, and command templates so they reflect new or removed principles, then prepends a Sync Impact Report to the constitution. - Extension hooks: Executes optional or mandatory before/after hooks declared in .specify/extensions.yml. - Use Case: After deciding to add a new testing-discipline principle, run this Skill to amend the constitution to a new minor version and automatically flag which templates need matching updates. ## Quick Start Ask the assistant to update the project constitution with your principles, for example: "Update the project constitution to add a principle requiring integration tests for all public APIs."

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 spec-kit project constitution?

Provide your principles or values as input, and the Skill fills every placeholder in .specify/memory/constitution.md, bumps the version semantically, and writes the file back. It also validates dependent templates and reports which ones need updates.

How does constitution versioning work in spec-kit?

Versioning follows semantic rules: MAJOR for backward-incompatible principle removals or redefinitions, MINOR for new principles or expanded guidance, and PATCH for clarifications or typo fixes. If the bump type is ambiguous, the Skill proposes reasoning before finalizing.

What happens if the constitution file does not exist yet?

If .specify/memory/constitution.md is missing, it is first copied from .specify/templates/constitution-template.md, which is normally initialized during project setup. The Skill always operates on the existing constitution file rather than creating a new template.

Does the constitution update keep other spec-kit templates in sync?

Yes. The Skill reads plan-template.md, spec-template.md, tasks-template.md, and command files to verify alignment with updated principles, then prepends a Sync Impact Report listing updated or pending templates as an HTML comment.

What are extension hooks in a spec-kit constitution update?

Hooks are commands declared under hooks.before_constitution or hooks.after_constitution in .specify/extensions.yml. Optional hooks are suggested to the user, while mandatory hooks are executed automatically before the workflow continues.

What if required constitution information like the ratification date is unknown?

The Skill inserts a TODO(<FIELD_NAME>) placeholder with an explanation and lists it under deferred items in the Sync Impact Report. It never leaves unexplained bracket tokens in the final document.