speckit-constitution

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

44|10|Updated Mar 28, 2024
One-click install
npx skills add https://github.com/sensein/senselab --skill speckit-constitution-sensein
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/sensein/senselab/tree/main/.claude/skills/speckit-constitution
Command: npx skills add https://github.com/sensein/senselab --skill speckit-constitution-sensein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a project's governing principles consistent across the constitution file and all dependent spec-kit templates is error-prone manual work; this Skill fills the constitution template, versions changes, and propagates amendments automatically. ## Core Features & Use Cases - Constitution Authoring: Fills placeholder tokens in .specify/memory/constitution.md from user input or repository context, with semantic version bumping rules (MAJOR/MINOR/PATCH). - Template Synchronization: Validates and updates plan, spec, tasks, and command templates so they stay aligned with amended principles. - Sync Impact Report: Prepends an HTML comment report listing version changes, modified principles, and pending template updates. - Use Case: A team adopting spec-kit wants to codify five engineering principles; the Skill drafts the constitution, bumps the version, and flags which templates need follow-up edits. ## Quick Start Ask the assistant to update the project constitution with your principles, for example: "Update the constitution to add a principle requiring test coverage for all new features."

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 the template at .specify/memory/constitution.md, derives missing values from repo context, bumps the version semantically, and writes the completed file back.

How does constitution versioning work in spec-kit?

Versions follow semantic rules: MAJOR for backward-incompatible principle removals or redefinitions, MINOR for new principles or sections, and PATCH for clarifications or wording fixes. Ambiguous bumps are reasoned through before finalizing.

Does the constitution update sync other spec-kit templates?

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

What happens if the constitution file is missing?

If .specify/memory/constitution.md does not exist, it is initialized by copying .specify/templates/constitution-template.md before any placeholder filling begins.

What if required constitution information is unknown?

Missing critical values such as an unknown ratification date are inserted as TODO(<FIELD_NAME>) markers with an explanation, and listed as deferred items in the Sync Impact Report.