speckit-constitution

Update the project constitution template and propagate changes across dependent artifacts.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/EmpoweredHouse/accrete --skill speckit-constitution-empoweredhouse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/EmpoweredHouse/accrete/tree/main/skills/speckit-constitution
Command: npx skills add https://github.com/EmpoweredHouse/accrete --skill speckit-constitution-empoweredhouse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains a living project constitution in the repository, ensuring governance principles stay aligned with templates, prompts, and runtime behavior.

Core Features & Use Cases

  • Centralized constitution governance with automatic template synchronization across .specify and related artifacts.
  • Versioning and amendment propagation to dependent artifacts and prompts.
  • Validation and consistency checks to prevent placeholders drift and ensure compliance across templates.

Quick Start

Provide inputs for the constitution values or let the tool derive them from the repository, then run the update process to overwrite the constitution and generate a Sync Impact Report.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema
How do I automate governance constitution updates and sync them across templates?

You can automate governance constitution updates by editing the template at .specify/memory/constitution.md. The tool propagates changes across dependent templates, validates placeholders, and generates a Sync Impact Report with versioning and compliance checks.

What is a Sync Impact Report for constitution versioning and compliance?

A Sync Impact Report is generated after constitution updates to document versioning increments, ratification dates, and compliance checks. It ensures governance principles stay aligned across dependent templates and artifacts without manual tracking.

How do I prevent placeholder drift in governance templates after policy changes?

Prevent placeholder drift by running the constitution sync process, which validates all placeholders across dependent templates and artifacts. This consistency check ensures governance principles remain compliant and aligned after every policy update.

Can I derive constitution values from repository context instead of providing explicit inputs?

Yes, the constitution sync tool accepts explicit input values or derives them directly from repository context. It then updates ratification and amendment dates and increments the constitution version automatically based on the derived data.

What's the best way to propagate amendment dates to dependent artifacts in a repository?

Propagate amendment dates by updating the centralized constitution template at .specify/memory/constitution.md. The sync process automatically propagates versioning and amendment dates to dependent artifacts, prompts, and related .specify files.

Do I need a .specify directory structure to use constitution governance automation?

Yes, the constitution governance automation requires a .specify directory structure to function. It specifically targets the .specify/memory/constitution.md file and synchronizes changes across related artifacts within that directory hierarchy.