speckit-constitution

Populate constitution templates with principle values and generate a Sync Impact Report.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/kamalsroor1/nest-scaffolding-crud-manager --skill speckit-constitution-kamalsroor1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/kamalsroor1/nest-scaffolding-crud-manager/tree/main/.agent/skills/speckit-constitution
Command: npx skills add https://github.com/kamalsroor1/nest-scaffolding-crud-manager --skill speckit-constitution-kamalsroor1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual, error-prone work of updating a project's governance document and ensuring all dependent templates and runtime guidance remain consistent after changes to principles or versioning.

Core Features & Use Cases

  • Template Filling: Locate placeholder tokens in the constitution template, derive or collect concrete values, and replace tokens precisely.
  • Consistency Propagation: Validate and update related templates and command docs in .specify/templates to keep task plans, specs, and commands aligned with amended principles.
  • Governance Versioning & Reporting: Apply semantic versioning rules for constitution changes, produce a Sync Impact Report with changed sections and follow-up TODOs, and write the updated constitution back to memory.
  • Use Case: When a project adds a new principle or clarifies an existing one, use this Skill to update the constitution, bump the version appropriately, and surface template files requiring follow-up.

Quick Start

Update the constitution at .specify/memory/constitution.md using repository context and any provided principle inputs, then propagate changes to templates and produce 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 and keep dependent templates consistent?

To update a project constitution, populate the constitution template with concrete principle values and propagate changes to related .specify/templates. This ensures task plans, specs, and command docs remain aligned with amended governance principles.

What is semantic versioning for constitution changes in a spec-kit layout?

Semantic versioning for constitution changes involves applying version bump rules when principles are added, amended, or ratified. This tracks governance evolution and triggers a Sync Impact Report detailing changed sections and follow-up TODOs.

How do I fill placeholder tokens in a constitution template automatically?

Filling placeholder tokens in a constitution template requires locating the tokens, deriving or collecting concrete values from repository context, and replacing them precisely. This populates the governance document with actual principle definitions.

Do I need a .specify directory to synchronize project governance documents?

Yes, a .specify directory is required to synchronize project governance documents. This layout stores the constitution.md memory file, related templates, and extensions.yml hooks needed to parse governance extensions and apply versioning rules.

What does a Sync Impact Report include when amending project principles?

A Sync Impact Report includes changed constitution sections and follow-up TODOs when amending project principles. It surfaces template files requiring manual review after the automated consistency propagation and version bump are complete.

Can I parse extensions.yml hooks to update constitution governance rules?

Yes, you can parse .specify/extensions.yml hooks to update constitution governance rules. The Skill reads these extension hooks alongside the constitution template to apply semantic versioning and ensure all runtime guidance stays synchronized.