speckit-constitution

Resolve placeholder tokens in the project constitution and propagate governance updates.

Updated Feb 26, 2026

Search Tags:#automation #templates #versioning #consistency #constitution #governance #spec-kit

Ready to run

npx skills add https://github.com/tomlm/Boxcars --skill speckit-constitution-tomlm

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

Core Features & Use Cases

Automatic placeholder resolution and versioned governance
Template propagation across .specify templates and memory state
Consistency checks and cross-references to ensure alignment with downstream workflows

Quick Start

Update the constitution by supplying missing values and run the speckit-constitution workflow to 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 automate project constitution updates and sync governance templates?▼

Automate constitution updates by resolving placeholder tokens like RATIFICATION_DATE and CONSTITUTION_VERSION in .specify/memory/constitution.md, then propagating changes across dependent templates. This enforces versioned governance and consistency checks to ensure no bracket tokens remain.

What are placeholder tokens in a project constitution and how do I resolve them?▼

Placeholder tokens in a project constitution are bracketed variables like RATIFICATION_DATE, LAST_AMENDED_DATE, and CONSTITUTION_VERSION. Resolve them by supplying derived or user-provided values, enforcing validation to ensure no bracket tokens remain in the file.

How do I enforce versioning and consistency checks across governance templates?▼

Enforce versioning and consistency checks across governance templates by applying automated validation rules during constitution updates. This ensures all sections conform to defined policies and cross-references align with downstream workflows without leaving unresolved bracket tokens.

Can I update a project constitution without manually editing dependent templates?▼

Yes, you can update a project constitution without manual template edits by running an automated workflow that propagates governance updates across .specify templates and memory state. This automatically syncs all dependent artifacts with the latest constitution values.

Why do bracket tokens remain in my governance constitution after template updates?▼

Bracket tokens remain in your governance constitution when placeholder resolution fails or validation is skipped. Running the automated update workflow enforces consistency checks to guarantee all sections conform to policy and no bracket tokens are left behind.

What is the best way to maintain consistency between a project constitution and downstream workflows?▼

The best way to maintain consistency between a project constitution and downstream workflows is using automated template propagation and cross-reference validation. This synchronizes memory state and dependent artifacts, ensuring alignment when governance changes occur.