speckit-constitution

Synchronize project governance by propagating constitution changes to dependent specification templates.

34|2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/DengNaichen/Stet --skill speckit-constitution-dengnaichen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/DengNaichen/Stet --skill speckit-constitution-dengnaichen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that project-wide principles, governance rules, and documentation remain consistent and synchronized across all project templates and artifacts.

Core Features & Use Cases

  • Automated Template Syncing: Propagates changes from the project constitution to all dependent specification and task templates.
  • Governance Versioning: Manages semantic versioning for project principles and tracks ratification dates.
  • Use Case: When adding a new engineering principle to the project, use this Skill to automatically update the constitution, validate the change against existing templates, and generate a sync report to ensure no documentation drift occurs.

Quick Start

Invoke the speckit-constitution skill to update the project constitution with the new principle regarding asynchronous communication.

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 governance principles across multiple documentation templates?

To synchronize project governance, you can update the central constitution template and automatically propagate those changes to all dependent specification artifacts, ensuring documentation alignment and preventing drift across templates.

What is a constitution template and when do I need it for project governance?

A constitution template is a centralized document for maintaining project-wide principles and governance rules. You need it when adding or amending engineering principles to ensure changes are tracked and validated against existing templates.

How to manage semantic versioning for project principles and governance rules?

Manage semantic versioning for project principles by applying strict version tracking and ratification dates to the constitution template, ensuring that every amendment to governance rules is validated and version-controlled.

Does the .specify directory structure support automated template syncing for compliance?

Yes, operating within the .specify directory structure enables automated template syncing by maintaining alignment between memory files and operational templates, ensuring compliance and consistency across the project.

What's the best way to validate new engineering principles against existing specification artifacts?

The best way to validate new principles is to use template-based validation during the constitution update process, which automatically checks for alignment and generates a sync report to identify any documentation drift.

Why does documentation drift occur when updating project-wide governance rules?

Documentation drift occurs when governance rules are updated in isolation without propagating changes to dependent specification and task templates, a problem solved by synchronizing updates from the central constitution.