speckit-constitution

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

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-constitution-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-constitution-luandopke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a project's governing principles consistent across spec-kit artifacts is error-prone when done manually. This Skill fills the constitution template at .specify/memory/constitution.md with concrete values and propagates amendments to dependent templates. ## Core Features & Use Cases - Constitution Authoring: Collects or derives values for every placeholder token (project name, principles, governance dates) and writes a complete constitution. - Semantic Versioning of Governance: Automatically bumps CONSTITUTION_VERSION using MAJOR/MINOR/PATCH rules based on the nature of the changes. - Consistency Propagation: Validates and updates plan-template.md, spec-template.md, tasks-template.md, and related command files, then prepends a Sync Impact Report. - Use Case: After deciding to add a new testing-discipline principle, run this Skill to amend the constitution to a new minor version and flag every template that must reflect the new rule. ## Quick Start Ask the agent to update the project constitution with your new principle and keep all spec-kit templates in sync.

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?▼

Run the constitution command with your principle inputs. The Skill loads .specify/memory/constitution.md, replaces every bracketed placeholder with concrete values, and writes the completed file back with an updated version line.

How is the constitution version number incremented?▼

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. Ambiguous bumps are reasoned through before finalizing.

Does the constitution update affect other spec-kit templates?▼

Yes. The Skill reads plan-template.md, spec-template.md, and tasks-template.md to verify alignment with updated principles, then records each template as updated or pending in a Sync Impact Report prepended to the constitution.

What happens if the constitution file does not exist yet?▼

If .specify/memory/constitution.md is missing, the Skill copies the baseline from .specify/templates/constitution-template.md first, then proceeds with placeholder collection and filling as usual.

What are extension hooks in the constitution workflow?▼

Hooks are optional or mandatory commands declared in .specify/extensions.yml under before_constitution or after_constitution keys. Enabled hooks without conditions are invoked before or after the update, and the Skill waits for mandatory hooks to finish.