speckit-constitution

Update project constitutions and propagate changes to dependent templates in spec-kit projects.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/xyphyx/internal-project-template --skill speckit-constitution-xyphyx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/xyphyx/internal-project-template/tree/main/.claude/skills/speckit-constitution
Command: npx skills add https://github.com/xyphyx/internal-project-template --skill speckit-constitution-xyphyx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams maintain a living project constitution by synthesizing user-provided principles and aligning dependent templates and governance artifacts across the repository.

Core Features & Use Cases

  • Create or update the project constitution from interactive inputs or provided principle data.
  • Propagate changes to related templates, plans, and commands to keep governance in sync.
  • Support semantic versioning, governance updates, and memory propagation across the spec-kit structure.

Quick Start

Provide the guiding principles you want to apply, and the skill will update .specify/memory/constitution.md and propagate changes to dependent artifacts.

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 project constitution from guiding principles in a spec-kit repository?

You can create or update a project constitution by providing guiding principles interactively or as automated inputs. The skill synthesizes these principles, resolves placeholders, and propagates governance changes to dependent templates.

What is semantic versioning for project governance and how does it keep templates in sync?

Semantic versioning for project governance increments the CONSTITUTION_VERSION to track changes to guiding principles. This versioning ensures dependent templates, plans, and commands remain synchronized with the updated constitution.

Can I automate governance and memory propagation across a spec-kit project structure?

Yes, you can automate governance and memory propagation by providing principle data as automated inputs. The skill resolves placeholders to concrete values and propagates updates across the spec-kit structure without manual intervention.

Does project constitution management require a specific folder structure to work?

Yes, this skill requires a spec-kit project with a .specify folder. This directory structure stores the memory, governance artifacts, and task definitions needed to synchronize the project constitution.

What happens to dependent templates when I change a project constitution?

When you change a project constitution, the skill propagates updates to dependent templates, plans, and commands. It resolves placeholders to concrete values, ensuring all documentation aligns with the new principles.

Why does my project constitution need placeholder resolution before applying changes?

Placeholder resolution is needed to convert abstract template variables into concrete values during constitution updates. This ensures that propagated changes to documentation, plans, and commands contain actual data rather than unresolved syntax.