speckit.constitution — Claude Code prompt: setup and usage
speckit.constitution updates the project constitution template in .specify/memory/constitution.md and aligns dependent specification templates.
MIT ★ 110 updated 2026-10-19
.claude/commands/speckit.constitution.mdWhat speckit.constitution does
The prompt loads .specify/memory/constitution.md and finds uppercase tokens like [PROJECT_NAME] or [PRINCIPLE_1_NAME]. It replaces them with rules derived from the prompt arguments or repository context. Each principle is framed with unambiguous MUST or SHOULD statements. Revisions follow semantic versioning: MAJOR for breaking rule removals, MINOR for added sections, and PATCH for non-semantic edits.
It then inspects .specify/templates/plan-template.md, .specify/templates/spec-template.md, and task definitions to keep instructions consistent. A Sync Impact Report is prepended to the constitution as an HTML comment. The run concludes with a formatted commit message suggestion.
The routine requires an existing .specify/memory/constitution.md file in the repository. It will not generate a fresh template hierarchy from scratch.
What it helps with
- formalize engineering principles into a project constitution
- keep specification and task templates aligned with architecture rules
- track governance revisions with semantic versioning
- generate an impact report for changes in development guidelines
Example prompts for the agent
- Update the constitution with a non-negotiable rule on automated tests
- Populate
.specify/memory/constitution.mdplaceholders from repository docs - Bump the constitution version and check impact on
.specify/templates/
How to install speckit.constitution
Manually: put the files in place
.claude/commands/speckit.constitution.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about speckit.constitution
How to install speckit.constitution in Claude Code?
Place the prompt contents into .claude/commands/speckit.constitution.md. Claude Code will automatically make it available as a workspace command.
What does speckit.constitution do?
It fills placeholder tokens in .specify/memory/constitution.md, bumps the governance version, and checks dependent specification templates for consistency.
How does it decide the version bump?
It applies SemVer logic: MAJOR bumps for backward-incompatible rule removals, MINOR for new principles or sections, and PATCH for minor wording fixes.
Source text
speckit.constitution.md · MIT
---
description: Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
handoffs:
- label: Build Specification
agent: speckit.specify
prompt: Implement the feature specification based on the updated constitution. I want to build...
---
## User Input
```text
$ARGUMENTS
```
You **MUST** consider the user input before proceeding (if not empty).
## Outline
You are updating the project constitution at `.specify/memory/constitution.md`. This file is a TEMPLATE containing placeholder tokens in square brackets (e.g. `[PROJECT_NAME]`, `[PRINCIPLE_1_NAME]`). Your job is to (a) collect/derive concrete values, (b) fill the template precisely, and (c) propagate any amendments across dependent artifacts.
Follow this execution flow:
1. Load the existing constitution template at `.specify/memory/constitution.md`.
- Identify every placeholder token of the form `[ALL_CAPS_IDENTIFIER]`.
**IMPORTANT**: The user might require less or more principles than the ones used in the template. If a number is specified, respect that - follow the general template. You will update the doc accordingly.
2. Collect/derive values for placeholders:
- If user input (conversation) supplies a value, use it.
- Otherwise infer from existing repo context (README, docs, prior constitution versions if embedded).
- For governance dates: `RATIFICATION_DATE` is the original adoption date (if unknown ask or mark TODO), `LAST_AMENDED_DATE` is today if changes are made, otherwise keep previous.
- `CONSTITUTION_VERSION` must increment according to semantic versioning rules:
- MAJOR: Backward incompatible governance/principle removals or redefinitions.
- MINOR: New principle/section added or materially expanded guidance.
- PATCH: Clarifications, wording, typo fixes, non-semantic refinements.
- If version bump type ambiguous, propose reasoning before finalizing.
3. Draft the updated constitution content:
- Replace every placeholder with concrete text (no bracketed tokens left except intentionally retained template slots that the project has chosen not to define yet—explicitly justify any left).
- Preserve heading hierarchy and comments can be removed once replaced unless they still add clarifying guidance.
- Ensure each Principle section: succinct name line, paragraph (or bullet list) capturing non‑negotiable rules, explicit rationale if not obvious.
- Ensure Governance section lists amendment procedure, versioning policy, and compliance review expectations.
4. Consistency propagation checklist (convert prior checklist into active validations):
- Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles.
- Read `.specify/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints.
- Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline).
- Read each command file in `.specify/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required.
- Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed.
5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update):
- Version change: old → new
- List of modified principles (old title → new title if renamed)
- Added sections
- Removed sections
- Templates requiring updates (✅ updated / ⚠ pending) with file paths
- Follow-up TODOs if any placeholders intentionally deferred.
6. Validation before final output:
- No remaining unexplained bracket tokens.
- Version line matches report.
- Dates ISO format YYYY-MM-DD.
- Principles are declarative, testable, and free of vague language ("should" → replace with MUST/SHOULD rationale where appropriate).
7. Write the completed constitution back to `.specify/memory/constitution.md` (overwrite).
8. Output a final summary to the user with:
- New version and bump rationale.
- Any files flagged for manual follow-up.
- Suggested commit message (e.g., `docs: amend constitution to vX.Y.Z (principle additions + governance update)`).
Formatting & Style Requirements:
- Use Markdown headings exactly as in the template (do not demote/promote levels).
- Wrap long rationale lines to keep readability (<100 chars ideally) but do not hard enforce with awkward breaks.
- Keep a single blank line between sections.
- Avoid trailing whitespace.
If the user supplies partial updates (e.g., only one principle revision), still perform validation and version decision steps.
If critical info missing (e.g., ratification date truly unknown), insert `TODO(<FIELD_NAME>): explanation` and include in the Sync Impact Report under deferred items.
Do not create a new template; always operate on the existing `.specify/memory/constitution.md` file.
© alfredoperez · MIT · alfredoperez/speckit-companion