speckit-constitution

Replace ALL_CAPS placeholders in .specify/memory/constitution.md and synchronize dependent templates.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ins-enco/ctm__affiliate_backend --skill speckit-constitution-ins-enco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/ins-enco/ctm__affiliate_backend/tree/main/.claude/skills/speckit-constitution
Command: npx skills add https://github.com/ins-enco/ctm__affiliate_backend --skill speckit-constitution-ins-enco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates creating and updating a project's constitution by locating and replacing ALL_CAPS placeholder tokens in the .specify/memory/constitution.md template, determining appropriate version bumps and dates, and propagating those changes across dependent templates to prevent governance drift and manual inconsistencies.

Core Features & Use Cases

  • Template population: Collect user-supplied or inferred values, replace placeholders, and ensure no unexplained tokens remain.
  • Versioning & governance: Determine and apply MAJOR/MINOR/PATCH version increments, set ISO-format dates, and include a Sync Impact Report summarizing changes.
  • Consistency propagation: Validate and update related files under .specify/templates and command docs, and flag follow-up TODOs for manual review.
  • Use Case: Maintainers adopting new principles can run this Skill to update the constitution file, bump the governance version, and align all spec-kit templates automatically.

Quick Start

Update the project constitution by filling placeholders in .specify/memory/constitution.md, apply a semantic version bump with rationale, and synchronize affected .specify/templates files.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema
How do I update project constitution templates and keep governance documentation in sync?

To update project constitution templates, replace ALL_CAPS placeholders in the .specify/memory/constitution.md file, apply a semantic version bump, and synchronize changes across related .specify/templates files to prevent governance drift.

What is a spec-kit repository and how does template-driven governance work?

A spec-kit repository uses a .specify directory to manage template-driven governance. It works by parsing placeholders in the constitution.md file and propagating values to dependent templates to maintain project consistency.

How do I apply semantic version bumps to a project constitution file?

To apply semantic version bumps to a project constitution, determine MAJOR, MINOR, or PATCH increments based on changes, set ISO-format dates, and generate a Sync Impact Report summarizing the governance updates.

Does updating constitution placeholders require a specific repository structure?

Updating constitution placeholders requires a repository structure that includes a .specify directory. The process reads and writes to .specify/memory/constitution.md and updates related files under .specify/templates.

What happens if unexplained placeholder tokens remain in the constitution file?

If unexplained placeholder tokens remain in the constitution file, the template population process fails to ensure no ALL_CAPS tokens are left behind, requiring user-supplied or inferred values to complete the governance documentation.

Can I automate consistency propagation for spec-kit command files and templates?

You can automate consistency propagation for spec-kit command files and templates by validating and updating related files under .specify/templates, automatically flagging follow-up TODOs for manual review after governance changes.