speckit-constitution

Update Specify-based constitution placeholders, dates, and versioning with a Sync Impact Report.

Updated May 28, 2026
One-click install
npx skills add https://github.com/bdunnette/reaper --skill speckit-constitution-bdunnette
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/bdunnette/reaper/tree/main/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/bdunnette/reaper --skill speckit-constitution-bdunnette

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates updating the project constitution based on user inputs and repository context.

Core Features & Use Cases

  • Updates placeholders, ratification and amendment dates, and versioning across the constitution.
  • Validates and propagates governance changes to dependent templates and tasks.
  • Generates a Sync Impact Report to document changes and rationale.

Quick Start

Update the constitution using your inputs and the repository context, then review the Sync Impact Report and commit.

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema
How do I automate governance constitution updates for a software project?

Automating governance constitution updates involves replacing placeholders, synchronizing ratification dates, and propagating versioning across principles to produce an updated constitution and a Sync Impact Report.

What is a Sync Impact Report in project governance?

A Sync Impact Report documents applied governance changes and their rationale, ensuring that placeholder replacements and version updates across the constitution are fully traceable and validated.

How do I sync ratification and amendment dates across multiple governance principles?

Syncing ratification and amendment dates requires validating user inputs and repository context, then automatically propagating the RATIFICATION_DATE and LAST_AMENDED_DATE across all dependent principles.

How to handle placeholder replacement in a Specify-based constitution template?

Handling placeholder replacement in a Specify-based constitution template requires validating inputs against repository context, replacing placeholders, and preserving existing governance rules during the update.

Does this constitution versioning approach validate inputs before updating governance rules?

Yes, input validation occurs before updating governance rules, ensuring that placeholder replacement, date synchronization, and version changes preserve the integrity of the constitution.

Can I propagate governance changes to dependent templates and tasks automatically?

Propagating governance changes to dependent templates and tasks is supported, automatically validating and syncing versioning and dates to maintain consistency across the project structure.