spec-constitution

Manage project constitution lifecycle and synchronize dependent templates in spec-kit repositories.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/eavichay/mycli --skill spec-constitution-eavichay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-constitution
Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/spec-constitution
Command: npx skills add https://github.com/eavichay/mycli --skill spec-constitution-eavichay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of maintaining consistency across a project's architectural principles, governance documentation, and supporting templates, ensuring that updates to the constitution propagate correctly to all dependent artifacts.

Core Features & Use Cases

  • Automated Constitution Updates: Manages the lifecycle of the project constitution, including versioning, placeholder replacement, and principle refinement.
  • Consistency Propagation: Automatically checks and updates dependent templates like plans, specs, and task definitions to ensure alignment with the core constitution.
  • Use Case: When a team decides to adopt a new development principle, this Skill ensures the change is reflected in the constitution, the project plan template, and the task categorization rules simultaneously.

Quick Start

Invoke the spec-constitution skill to update the project constitution with the new principle regarding asynchronous task processing.

Frequently Asked Questions about spec-constitution

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

FAQPage Schema
How do I synchronize project principles and governance documentation across templates?

Project principles and governance documentation synchronization propagates architectural changes from a central constitution file to dependent templates, ensuring automated cross-artifact consistency within a spec-kit structured repository.

What is the best way to manage semantic versioning for architectural principles?

Semantic versioning for architectural principles is managed by tracking the constitution file lifecycle, resolving placeholders, and applying version increments to ensure dependent plans and specs reflect the latest governance updates.

How do you update a project constitution and dependent templates simultaneously?

Updating a project constitution and dependent templates simultaneously involves modifying the core principle, then triggering consistency propagation to automatically align plans, specs, and task definitions with the new governance rules.

Do I need a valid .specify directory structure to manage constitution files?

A valid .specify directory structure is strictly required to manage constitution files, as it provides the necessary environment for placeholder resolution, semantic versioning, and cross-artifact consistency checks.

Why are my project plan templates not reflecting recent governance updates?

Project plan templates failing to reflect governance updates usually indicates a broken consistency propagation chain, requiring a cross-artifact consistency check to verify alignment with the core constitution file.

Can I use spec-constitution for automated compliance checks across architectural artifacts?

Automated compliance checks across architectural artifacts are supported by validating dependent templates against the core constitution, ensuring that all plans, specs, and task definitions adhere to defined governance principles.