speckit-constitution

Synchronize constitution templates with dependent specification and task artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of configuration drift between a project's core principles and its operational templates, ensuring that governance documentation remains accurate and consistent across the entire repository.

Core Features & Use Cases

  • Automated Template Sync: Automatically propagates changes from the project constitution to dependent planning and task templates.
  • Governance Versioning: Manages semantic versioning for project principles, ensuring clear audit trails for governance changes.
  • Use Case: When a team decides to adopt a new engineering principle, this skill updates the constitution and automatically flags all related task and specification templates that require manual review or alignment.

Quick Start

Invoke the speckit-constitution skill to update the project constitution with your new principles and synchronize all 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 synchronize project principles and governance documentation automatically?

You can synchronize project principles by invoking the governance skill to propagate changes from the project constitution to dependent specification and task templates.

How does automated template sync prevent configuration drift in a repository?

Automated template sync prevents configuration drift by validating template integrity and automatically flagging dependent specification and task templates that require manual review when principles update.

What is the best way to manage semantic versioning for engineering governance changes?

Managing semantic versioning for governance changes requires tracking principle updates within the .specify directory structure, ensuring clear audit trails across the project lifecycle.

Do I need a specific directory structure to enforce project governance rules?

Yes, this governance enforcement operates within the .specify directory structure to validate template integrity and apply versioning policies to dependent artifacts.

Can I flag outdated specification templates when adopting a new engineering principle?

Yes, updating the constitution with a new principle automatically flags all related task and specification templates that require manual review or alignment.

Why does governance documentation become inconsistent across a repository?

Governance documentation becomes inconsistent due to configuration drift between core principles and operational templates when updates are not propagated automatically across the project lifecycle.