speckit-constitution

Create and synchronize project constitutions within spec-kit .specify/ structures.

1|Updated Apr 7, 2025
One-click install
npx skills add https://github.com/RedFox-Soft/OAuth-server.ts --skill speckit-constitution-redfox-soft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/RedFox-Soft/OAuth-server.ts/tree/main/.claude/skills/speckit-constitution
Command: npx skills add https://github.com/RedFox-Soft/OAuth-server.ts --skill speckit-constitution-redfox-soft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating or updating a project constitution, ensuring that all related templates and files remain in sync.

Core Features & Use Cases

  • Constitution Creation/Update: Generate or modify the project constitution based on user input or interactive prompts.
  • Template Synchronization: Keep all dependent templates, such as plans, specifications, and tasks, up to date with any constitution changes.
  • Extension Hooks Support: Execute optional and mandatory hooks before and after constitution updates to handle additional processing or validation.

Quick Start

Create a new project constitution by running the following command: /update-constitution --principles "Open Source, Quality Code, Community Involvement".

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 creation and keep dependent templates in sync?

Automating project constitution creation and template synchronization involves generating the constitution file from input principles and propagating those updates across all dependent plans, specifications, and task templates within the project.

What is a project constitution in spec-kit and when do I need to update it?

A project constitution in spec-kit defines core principles like Open Source or Quality Code guiding development. You need to update it when project goals evolve, ensuring dependent templates and files remain synchronized with the new directives.

Does template synchronization for project constitutions require a specific directory structure?

Yes, template synchronization requires the spec-kit project structure containing a `.specify/` directory. This environment is strictly necessary to handle template propagation and execute extension hooks during constitution updates.

How do extension hooks work during constitution updates?

Extension hooks execute before and after constitution updates to handle additional processing or validation. These mandatory and optional hooks ensure custom logic and code governance are applied during template synchronization.

What is the best way to add new principles to an existing project constitution?

The best way to add principles to a project constitution is running an update command with a principles flag, passing comma-separated values like 'Open Source, Quality Code' to trigger interactive template-driven generation and synchronization.

Why are my dependent specification templates not updating after a constitution change?

Dependent specification templates fail to update when the project lacks the required `.specify/` directory or if mandatory extension hooks fail validation. Proper spec-kit structure and hook execution are required for successful template propagation.