speckit-constitution

Create or update the project constitution file from principle inputs.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Powerworks/Underwriting --skill speckit-constitution-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/Powerworks/Underwriting/tree/main/.claude/skills/speckit-constitution
Command: npx skills add https://github.com/Powerworks/Underwriting --skill speckit-constitution-powerworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using Spec Kit need a governed project constitution that defines non-negotiable principles, but writing and versioning it consistently is error-prone. This Skill fills the constitution template at .specify/memory/constitution.md with concrete values, enforces semantic versioning, and validates the result. ## Core Features & Use Cases - Template Placeholder Resolution: Identifies every [ALL_CAPS] token in the constitution template and fills it from user input or repository context. - Semantic Versioning of Governance: Automatically bumps CONSTITUTION_VERSION using MAJOR/MINOR/PATCH rules and generates a Sync Impact Report. - Scope Guard & Extension Hooks: Separates governance content from feature requests, defers non-governance intents, and runs before/after hooks defined in .specify/extensions.yml. - Use Case: A team lead wants to add a new testing principle to their Spec Kit project. They provide the principle text, and the Skill updates the constitution, bumps the minor version, and reports the changes. ## Quick Start Update the project constitution with these principles: code quality, test coverage, and documentation standards.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema
How do I update the project constitution in Spec Kit?▼

Provide your principles or values as input, and the Skill fills the template at .specify/memory/constitution.md, replacing all placeholder tokens. It validates the result, bumps the version semantically, and writes the file back.

How does constitution versioning work in Spec Kit?▼

The constitution uses semantic versioning: MAJOR for backward-incompatible principle removals, MINOR for new principles or sections, and PATCH for clarifications. The Skill proposes a bump type with reasoning when the change is ambiguous.

What happens if the constitution file does not exist?▼

If .specify/memory/constitution.md is missing, the Skill copies it from .specify/templates/constitution-template.md before filling placeholders. It never creates a new template from scratch.

Can the constitution command also implement features I mention?▼

No. A scope guard classifies input as governance content or non-governance intent. Feature implementation requests are deferred and listed in a Next Actions section with suggested follow-up commands like /speckit-specify.

What are extension hooks in the constitution workflow?▼

Hooks are commands defined under hooks.before_constitution or hooks.after_constitution in .specify/extensions.yml. Mandatory hooks execute automatically around the update, while optional hooks are suggested for manual invocation.