speckit-constitution

Automates versioning, placeholder replacement, and consistency validation of project constitution files.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/fmbetancourt/famifinances --skill speckit-constitution-fmbetancourt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/fmbetancourt/famifinances/tree/main/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/fmbetancourt/famifinances --skill speckit-constitution-fmbetancourt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that project principles and governance rules remain consistent, version-controlled, and synchronized across all project documentation and templates.

Core Features & Use Cases

  • Constitution Management: Automates the creation, versioning, and updating of the project constitution file.
  • Consistency Propagation: Validates and updates dependent templates like plans, specs, and tasks to ensure alignment with core principles.
  • Use Case: When a team decides to adopt a new development principle, this skill updates the constitution, increments the version, and verifies that all associated project templates reflect the change.

Quick Start

Invoke the speckit-constitution skill to update the project constitution with the latest principles and synchronize all dependent documentation.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema
How do I keep project governance principles consistent across all documentation templates?

Project governance principles are kept consistent by managing a central constitution file that automates versioning, placeholder replacement, and consistency validation across all dependent project templates. This ensures every document aligns with core rules.

What is a project constitution file used for in software engineering?

A project constitution file is used to define and maintain core development principles and governance rules. It acts as the single source of truth, ensuring that all project documentation, plans, and specs remain synchronized with established standards.

How do I automate versioning for project principles and governance documents?

Automating versioning for project principles is done by updating the central constitution file, which automatically increments the version and verifies that all associated project templates reflect the new governance changes.

Do I need a specific directory structure to maintain project governance integrity?

Yes, maintaining project governance integrity requires a structured .specify directory. This directory architecture is necessary to support the lifecycle management and synchronization of the constitution files and dependent templates.

How do I update dependent project templates when a new development principle is adopted?

Dependent templates are updated automatically when the central constitution is modified. The system propagates the new principle across plans, specs, and tasks, validating consistency to ensure all documentation reflects the updated governance.

What happens if my project documentation templates lose alignment with core principles?

When documentation loses alignment, consistency validation identifies the discrepancies. Updating the constitution file triggers synchronization, which replaces placeholders and verifies that all templates correctly reflect the current governance.