speckit.constitution

Update constitution templates, validate placeholders, bump semantic versions, and write sync impact reports.

Updated Oct 4, 2025
One-click install
npx skills add https://github.com/peancharoen/lcbp3 --skill speckit-constitution-peancharoen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.constitution
Source: https://github.com/peancharoen/lcbp3/tree/main/.agents/skills/speckit.constitution
Command: npx skills add https://github.com/peancharoen/lcbp3 --skill speckit-constitution-peancharoen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill automates updating the project's constitution template, removing manual drift between governance principles and operational templates, and ensuring amendments are tracked, versioned, and propagated consistently.

Core Features & Use Cases

  • Placeholder Resolution: Detects all [ALL_CAPS_IDENTIFIER] tokens in the constitution template and replaces them with user-supplied or inferred values from repository context.
  • Governance Versioning: Applies semantic versioning rules to determine MAJOR/MINOR/PATCH bumps, sets ISO governance dates, and documents rationale when ambiguous.
  • Propagation & Validation: Updates dependent templates and command docs, runs a checklist to validate no unexplained tokens remain, and prepends a Sync Impact Report to the constitution file.
  • Auditable Output: Writes the completed constitution to .specify/memory/constitution.md and produces a clear summary and suggested commit message for maintainers.
  • Use Case: When governance principles change during a release, run the skill to fill the constitution template, update templates, and create an auditable impact report.

Quick Start

Use the speckit.constitution skill to update .specify/memory/constitution.md by replacing placeholders from repository context, deciding the semantic version bump, and generating 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 update a project constitution template and keep governance principles synchronized?

To update a project constitution template and keep governance synchronized, replace placeholder tokens with repository context, apply semantic versioning, and generate a sync impact report to ensure operational templates remain consistent.

How does semantic versioning work for governance principles and constitution amendments?

Semantic versioning for governance principles determines MAJOR, MINOR, or PATCH bumps when constitution principles change, sets ISO governance dates, and documents rationale to track amendments consistently across repository templates.

What is the best way to resolve placeholder tokens in a constitution template automatically?

Resolving placeholder tokens in a constitution template involves detecting all bracketed identifiers and replacing them with user-supplied or inferred repository context values, validating that no unexplained tokens remain in the final output.

How do I audit constitution changes and propagate updates to dependent spec and plan templates?

Auditing constitution changes and propagating updates requires modifying dependent spec and plan templates, running a validation checklist for remaining tokens, and prepending a sync impact report to the constitution file for maintainers.

Can I use this constitution synchronization workflow for repository governance during a release?

Yes, this constitution synchronization workflow fits repository governance during a release by filling the constitution template, updating dependent governance templates, and creating an auditable impact report with a suggested commit message.

Why does manual drift occur between governance principles and operational templates?

Manual drift between governance principles and operational templates occurs when updating constitution files by hand without automated synchronization, leading to inconsistent placeholders, untracked version changes, and missing audit reports across dependent documents.