speckit-constitution

Create or update project constitutions with placeholders, amendments, and formatting validation.

Updated Aug 23, 2026

Search Tags:#templates #versioning #compliance #constitution #governance #principles

Ready to run

npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-constitution-leonardomoraisf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/leonardomoraisf/commonplace-pinboard-extension/tree/main/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/leonardomoraisf/commonplace-pinboard-extension --skill speckit-constitution-leonardomoraisf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It establishes a repeatable, living governance document by creating or updating the project constitution. It ensures code quality, testing standards, and architectural constraints are defined at project start and kept in sync as the project evolves.

Core Features & Use Cases

Initiates or updates the constitution at .specify/memory/constitution.md, replacing placeholders with concrete values.
Propagates amendments across related artifacts and dependent documents whenever governance changes.
Validates formatting and consistency, produces a Sync Impact Report, and enforces a standardized governance workflow.

Quick Start

Run the constitution sync to fill placeholders in .specify/memory/constitution.md using current repository context.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema

How do I create a project constitution to define governance rules upfront?▼

To create a project constitution, initiate a sync to fill placeholders in .specify/memory/constitution.md with current repository context. This drafts principled rules and establishes a repeatable governance document defining code quality and architectural constraints.

How does amendment propagation work when updating project governance?▼

Amendment propagation works by applying updates to the constitution and automatically propagating those changes across related artifacts and dependent documents. This ensures governance documents stay in sync and produces a Sync Impact Report to validate consistency.

What is the best way to maintain versioning and formatting consistency for a project constitution?▼

The best way to maintain versioning consistency is using a standardized governance workflow that validates formatting, enforces declarative language, and ensures standardized dates. This strict formatting validation keeps the constitution document consistent across project updates.

When do I need to establish project governance and constitutional principles?▼

You need to establish project governance at project start to define code quality, testing standards, and architectural constraints. You should also update governance whenever project principles evolve, ensuring the constitution remains a living document throughout the project lifecycle.

Can I update an existing constitution document without breaking dependent artifacts?▼

Yes, you can update an existing constitution without breaking dependent artifacts. The sync process propagates amendments across related documents and generates a Sync Impact Report, validating that formatting, dates, and declarative language remain consistent across all dependent artifacts.

Why does my project constitution need a Governance section and amendment procedures?▼

A project constitution needs a Governance section and amendment procedures to ensure strict formatting and establish a repeatable, living governance document. These sections define how rules evolve, ensuring code quality standards and architectural constraints are maintained as the project scales.