speckit-constitution

Synchronize governance principles and versioning across dependent project templates.

Updated Jun 5, 2026

Search Tags:#templates #documentation #synchronization #constitution #governance #project-management

Ready to run

npx skills add https://github.com/estaciolima/idle-improvement-game --skill speckit-constitution-estaciolima

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/estaciolima/idle-improvement-game/tree/main/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/estaciolima/idle-improvement-game --skill speckit-constitution-estaciolima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the maintenance of a project constitution, ensuring that governance principles, versioning, and project-wide templates remain synchronized and consistent as the project evolves.

Core Features & Use Cases

Template Synchronization: Automatically propagates principle changes across project plans, specifications, and task templates.
Governance Versioning: Manages semantic versioning for the constitution based on the nature of governance changes.
Use Case: When adding a new development principle to your project, use this skill to update the constitution and ensure all dependent documentation and task templates are updated to reflect the new requirement.

Quick Start

Use the speckit-constitution skill to update the project constitution with the new principle regarding automated testing requirements.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema

How do I synchronize governance principles across project documentation templates?▼

You can synchronize governance principles across project documentation templates by updating the project constitution file, which automatically propagates changes to dependent plans, specifications, and task templates to maintain consistency.

What is project constitution versioning and when do I need to update it?▼

Project constitution versioning tracks governance changes using semantic versioning. You need to update it when adding or modifying development principles to ensure all dependent documentation reflects the new requirements.

How do I manage project governance principles within the .specify directory structure?▼

You manage project governance principles within the .specify directory structure by updating the constitution file, which synchronizes memory files and operational documentation through template-based placeholder replacement logic.

Does this approach to governance documentation work without external dependencies?▼

Yes, this governance documentation approach works without external dependencies. It operates entirely within the .specify directory structure to synchronize memory files and operational documentation using semantic versioning and placeholder replacement.

What's the best way to automate updates to project governance and task templates?▼

The best way to automate updates to project governance and task templates is through constitution synchronization, which propagates principle changes across all dependent project plans and specifications automatically.

Why does my project constitution documentation get out of sync with task templates?▼

Project constitution documentation gets out of sync with task templates when governance principles are updated manually without propagating changes. Automating template synchronization ensures memory files and operational documentation remain consistent.