skills.rest
fly-eng
fly-engCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

speckit-constitution

Update project constitution placeholders and sync dependent templates in spec-kit repositories.

Updated Apr 23, 2026
Search Tags:#automation#templates#versioning#constitution#governance#placeholders
One-click install
npx skills add https://github.com/fly-eng/yzh --skill speckit-constitution-fly-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/fly-eng/yzh/tree/main/.kimi/skills/speckit-constitution
Command: npx skills add https://github.com/fly-eng/yzh --skill speckit-constitution-fly-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

Core Features & Use Cases

  • Update the constitution at .specify/memory/constitution.md by replacing tokens like [PROJECT_NAME].
  • Collect and derive values for placeholders, manage governance dates, and increment CONSTITUTION_VERSION per semantic rules.
  • Propagate amendments across dependent artifacts and generate a Sync Impact Report for traceability.

Quick Start

Provide input values to update the constitution at .specify/memory/constitution.md and propagate amendments across dependent artifacts.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema
How do I automate project constitution updates and sync dependent templates?▼

To automate constitution updates, the Skill replaces interactive input placeholders like [PROJECT_NAME] and propagates amendments across dependent templates, generating a Sync Impact Report for traceability.

What is a project constitution and when do I need versioning for governance?▼

A project constitution defines core governance principles within a .specify directory. You need versioning when amending principles requires incrementing CONSTITUTION_VERSION per semantic rules to maintain artifact traceability.

Does this constitution automation work with spec-kit style repositories?▼

Yes, this automation is designed specifically for spec-kit style repositories containing a .specify directory, requiring mandatory YAML frontmatter in SKILL.md to safely replace placeholders.

How do I manage governance dates and placeholder values in a constitution?▼

Manage governance dates and placeholder values by providing interactive or derived inputs, which the Skill uses to safely replace tokens and increment CONSTITUTION_VERSION per semantic rules.

What are the limitations of automating constitution governance with placeholders?▼

Limitations include strict dependency on the .specify directory structure and mandatory YAML frontmatter in SKILL.md. Without these prerequisites, safe placeholder replacement and template syncing cannot execute.

Related Skills

Explore More Legal & Compliance Skills→
sdk451sdk451

speckit-constitution

Update .specify/memory/constitution.md from interactive or provided principle inputs.

Community
Advanced
GratefulJinx77GratefulJinx77

speckit-constitution

Update project constitutions by resolving placeholders and incrementing semantic versions.

Community
Advanced
ev3rlitev3rlit

speckit-constitution

Create and maintain a project constitution with frontmatter metadata and version increments.

Community
Advanced
fhltafhlta

speckit-constitution

Create and update spec-kit project constitutions with semantic versioning and template sync.

Community
Advanced