speckit-constitution

Update project constitution placeholders, version history, and dependent templates.

Updated May 20, 2026
One-click install
npx skills add https://github.com/igmo71/Myrmex --skill speckit-constitution-igmo71
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/igmo71/Myrmex/tree/main/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/igmo71/Myrmex --skill speckit-constitution-igmo71

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The project constitution evolves and often drifts, causing governance gaps and inconsistent tooling.

Core Features & Use Cases

  • Automates constitution updates from interactive and programmatic inputs.
  • Synchronizes placeholders, version history, and dependent templates across the repository.
  • Supports governance-date handling, version bumps, and validation checks.

Quick Start

Provide your inputs or prompts to update the constitution, then run the update to synchronize all 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 keep governance rules current?

Automating project constitution updates requires applying interactive prompts and scripted inputs to replace placeholders, bump versions, and synchronize dependent templates across your repository. This ensures governance rules stay current and consistent.

What is the best way to synchronize version history and dependent templates across a repository?

Synchronizing version history and dependent templates is achieved by running automated validation checks that enforce required frontmatter, section structures, and ISO dates, while reporting the sync impact of your governance changes.

How do I validate frontmatter and section structure when updating governance docs?

Validating frontmatter and section structure during governance docs updates is handled by automated validation checks that enforce ISO dates and required formatting, ensuring changes meet the project constitution before synchronizing artifacts.

Does this automation support both interactive prompts and scripted inputs for versioning?

Yes, this automation supports both interactive prompts and programmatic scripted inputs to handle version bumps, update placeholders, and synchronize governance rules across your repository.

Why does my project constitution drift and cause governance gaps?

Project constitution drift happens when governance rules evolve without automated synchronization, causing inconsistent tooling and governance gaps. Automating updates and validating dependent templates prevents this drift.

When do I need automated governance date handling and version bumps for docs?

Automated governance date handling and version bumps are needed when updating your project constitution, ensuring ISO dates are enforced and dependent templates are synchronized to prevent governance gaps.