speckit-constitution

Update project constitutions from user principles and propagate changes across templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Updating and synchronizing a project constitution from interactive or provided principles to ensure governance remains consistent across templates and artifacts.

Core Features & Use Cases

  • Automates constitution updates from user inputs across the repository.
  • Propagates amendments to dependent templates and memory files to avoid drift.
  • Supports placeholder resolution, versioning, and governance compliance checks.

Quick Start

Provide initial principles or inputs to update the constitution and trigger automatic synchronization across templates.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema
How do I automatically update a project constitution from user inputs?

To update a project constitution automatically, you provide initial principles or interactive inputs, and the system derives concrete values to synchronize governance changes across the repository and dependent artifacts.

What is the best way to keep governance templates from drifting?

Keeping governance templates from drifting requires propagating constitution amendments directly to dependent memory files and templates, ensuring versioning rules and placeholder resolution are automatically enforced during updates.

How does versioning work for project governance principles?

Versioning for project governance principles works by enforcing specific versioning rules during constitution updates, tracking propagated changes across dependent templates to maintain strict compliance and synchronization.

Can I resolve placeholders across dependent governance artifacts?

Yes, you can resolve placeholders across dependent governance artifacts by deriving concrete values from interactive inputs and repository context, propagating those resolved values to keep templates compliant.

When do I need automated synchronization for project governance?

Automated synchronization for project governance is needed when you apply interactive inputs or repository context to update principles, requiring immediate propagation across dependent artifacts to prevent template drift.