speckit-constitution

Fill constitution template placeholders and sync dependent .specify templates.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/linhnguyen125/ClaudeCodeWithSpecKit --skill speckit-constitution-linhnguyen125
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/linhnguyen125/ClaudeCodeWithSpecKit/tree/main/.claude/skills/speckit-constitution
Command: npx skills add https://github.com/linhnguyen125/ClaudeCodeWithSpecKit --skill speckit-constitution-linhnguyen125

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual, error-prone work of maintaining a project's governance document and keeping all dependent templates aligned. It ensures the project's constitution is a single source of truth and that changes propagate consistently to plans, specs, tasks, and command guidance.

Core Features & Use Cases

  • Collects or infers concrete values for template placeholders and fills .specify/memory/constitution.md precisely.
  • Applies semantic versioning rules, manages ratification and amendment dates in ISO format, and emits a Sync Impact Report documenting changes.
  • Propagates and validates consistency across .specify templates (plan, spec, tasks, commands) and flags follow-up items for manual review.
  • Use case: update a principle name and rationale and automatically adjust template checks, spec scopes, and task categorizations across the repo.

Quick Start

Update the project constitution by filling placeholder tokens in .specify/memory/constitution.md, apply a version bump with rationale, and sync dependent templates.

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 placeholders and sync dependent templates automatically?▼

To update project constitution placeholders and sync dependent templates, this Skill parses bracketed placeholders in `.specify/memory/constitution.md`, fills them with concrete values, applies semantic versioning rules, and propagates changes across plan, spec, and task templates.

What is a spec-kit constitution and when do I need to sync it?▼

A spec-kit constitution is a governance document in `.specify/memory/constitution.md` that serves as a single source of truth. You need to sync it when updating principles, versioning, or ratification dates to ensure dependent templates remain consistent.

How do I apply semantic versioning to a project constitution in a spec-kit repository?▼

Semantic versioning is applied to a project constitution by updating the version field with a rationale, managing ratification and amendment dates in ISO format, and emitting a Sync Impact Report that documents all template modifications.

Does this template synchronization tool work with existing .specify directory structures?▼

Yes, template synchronization works directly with existing `.specify` directory structures. It reads and writes to `.specify/memory/constitution.md` and validates consistency across plan, spec, task, and command templates already present in the repository.

What are the limitations of syncing constitution templates across repository files?▼

Limitations of syncing constitution templates include flagging follow-up items requiring manual review after automated propagation, and dependency on a valid spec-kit structure with a `.specify` directory to function correctly.

What's the best way to maintain governance document consistency across spec-kit templates?▼

The best way to maintain governance document consistency is to use automated synchronization that propagates constitution changes to all dependent templates, validates alignment, and generates a Sync Impact Report to track modifications and flag manual review items.