speckit-constitution

Update .specify governance documents by merging user inputs and repo context.

180|11|Updated Apr 11, 2026

Search Tags:#automation #template #versioning #hooks #constitution #governance #spec-kit

Ready to run

npx skills add https://github.com/serverless-dna/tendril --skill speckit-constitution-serverless-dna

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/serverless-dna/tendril/tree/main/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/serverless-dna/tendril --skill speckit-constitution-serverless-dna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintaining a living constitution for a software project is error-prone and tedious. This skill updates the constitution file (.specify/memory/constitution.md) based on user input and existing repo context, ensuring governance rules and placeholders stay synchronized.

Core Features & Use Cases

Automatically merge user-supplied principle updates into the constitution template and memory file.
Increment constitution version numbers according to semantic changes and propagate amendments across templates.
Respect extension hooks and extension-driven guidance during the update process for safe governance edits.

Quick Start

Provide principle updates or inputs, and this skill will update the constitution accordingly.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema

How do I automate project constitution updates without breaking governance rules?▼

Automating project constitution updates requires merging user-supplied principles into the governance file while respecting existing repo context. This skill updates placeholders and governance sections in the .specify workflow, ensuring template consistency and safe governance edits via extension hooks.

What is the best way to propagate constitutional amendments across dependent artifacts?▼

Propagating amendments across dependent artifacts is handled by incrementing the constitution version numbers according to semantic changes. This skill automatically pushes template updates and synchronizes governance documents within the .specify memory directory.

How do I version a software project constitution when semantic changes occur?▼

Versioning a software project constitution involves incrementing version numbers based on the semantic impact of the input changes. This skill applies automated versioning to the constitution file and propagates those amendments across related templates.

Does the spec-kit workflow support extension hooks for governance document edits?▼

The spec-kit workflow supports extension hooks and extension-driven guidance during the governance update process. This skill respects those hooks to ensure safe, consistent edits to the constitution file and its placeholders.

Can I sync principle updates directly into my project's memory constitution file?▼

Syncing principle updates directly into the memory constitution file is the core function of this skill. It takes your user inputs and existing repo context to automatically update the .specify/memory/constitution.md file.

Why does manually editing a project constitution cause template inconsistencies?▼

Manually editing a project constitution causes template inconsistencies because placeholders and governance sections easily fall out of sync. This skill solves the problem by applying automated template consistency and propagating amendments across dependent artifacts.