speckit-constitution

Create and update project constitutions while propagating governance changes to dependent Spec Kit templates.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/AhmedRagabRG/academy --skill speckit-constitution-ahmedragabrg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-constitution
Source: https://github.com/AhmedRagabRG/academy/tree/main/frontend/.agents/skills/speckit-constitution
Command: npx skills add https://github.com/AhmedRagabRG/academy --skill speckit-constitution-ahmedragabrg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a project's governing constitution consistent with its specification, plan, and task templates is error-prone manual work. This Skill fills the constitution template with concrete principles, applies semantic versioning to amendments, and synchronizes all dependent Spec Kit artifacts automatically. ## Core Features & Use Cases - Constitution Authoring: Fills placeholder tokens in .specify/memory/constitution.md from user input or repository context, with semantic version bumping (MAJOR/MINOR/PATCH) and ISO-formatted governance dates. - Consistency Propagation: Validates and updates plan, spec, and tasks templates plus installed Spec Kit command files so they stay aligned with amended principles. - Sync Impact Report: Prepends an HTML comment report to the constitution listing version changes, modified principles, and templates requiring updates. - Extension Hooks: Executes optional or mandatory before/after hooks defined in .specify/extensions.yml. - Use Case: A team adopting Spec Kit wants to codify five engineering principles (e.g., test-first, observability) into their constitution and ensure every downstream template reflects the new governance rules. ## Quick Start Ask the agent to create or update the project constitution with your principles, for example: "Update the project constitution to add a principle requiring integration tests for all public APIs."

Frequently Asked Questions about speckit-constitution

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

FAQPage Schema
How do I create a project constitution with Spec Kit?▼

Run the constitution command with your principles as input, and it fills the template at .specify/memory/constitution.md with concrete values. If the file is missing, it is first copied from .specify/templates/constitution-template.md.

How does constitution versioning work in Spec Kit?▼

The constitution uses semantic versioning: MAJOR for backward-incompatible principle removals or redefinitions, MINOR for new principles or sections, and PATCH for clarifications or wording fixes. The version line is validated against the Sync Impact Report.

Does updating the constitution also update Spec Kit templates?▼

Yes. The workflow reads plan-template.md, spec-template.md, and tasks-template.md and checks that constitution checks, scope sections, and task categories align with the amended principles. A Sync Impact Report flags each template as updated or pending.

What happens if the ratification date is unknown?▼

If critical information like the ratification date cannot be determined, the workflow inserts a TODO(<FIELD_NAME>) marker with an explanation and lists it under deferred items in the Sync Impact Report rather than blocking the update.

Can the constitution command modify application source code?▼

No. A scope guard explicitly prohibits creating, modifying, or deleting application source files, routes, components, tests, or deployment files. Non-governance intents are deferred and listed in a Next Actions section with suggested follow-up commands.