Help us improve
Share bugs, ideas, or general feedback.
From constitution
Amend project constitution with semantic versioning and changelog management. Use when user asks to "amend constitution", "update constitution version", "add principle", or "modify governance rules". Automatically regenerates checklist.
npx claudepluginhub aaronbassett/agent-foundry --plugin constitutionHow this skill is triggered — by the user, by Claude, or both
Slash command
/constitution:amendThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are amending a project's CONSTITUTION.md with version tracking.
Creates or updates a project constitution from interactive or provided principle inputs, keeping dependent templates in sync via versioned amendments.
Creates or updates a project constitution (charter) by filling template placeholders, synchronizing changes across dependent templates and docs, and generating a versioned impact report.
Creates new constitution version directories for evolving architectural patterns, tech stacks, or rules. Migrates content to modular files, updates symlinks, and documents changes.
Share bugs, ideas, or general feedback.
You are amending a project's CONSTITUTION.md with version tracking.
Update constitutional principles with semantic versioning, maintain changelog (newest first), and automatically regenerate the implementation checklist.
Search for CONSTITUTION.md:
Parse version from footer:
*Version: X.Y.Z*
If not found: Assume 1.0.0
Interactive prompts:
Prompt 1: Amendment Type
What type of amendment?
1. MAJOR - Breaking change (removes/fundamentally changes core principles)
2. MINOR - Additive change (adds new principles)
3. PATCH - Clarification (typo fixes, wording improvements)
Choice [1-3]:
Prompt 2: Change Description
Describe the changes (2-5 sentences):
Prompt 3: Migration Notes (skip for PATCH)
Migration guidance for existing code (what needs to change?):
Prompt 4: Rationale
Why is this amendment necessary?
Rules:
MAJOR: X+1.0.0 (e.g., 2.3.1 → 3.0.0)
MINOR: X.Y+1.0 (e.g., 2.3.1 → 2.4.0)
PATCH: X.Y.Z+1 (e.g., 2.3.1 → 2.3.2)
Load template from:
${CLAUDE_PLUGIN_ROOT}/plugins/constitution/skills/amend/templates/amendment.template.md
Replace placeholders:
{{new_version}} → Calculated version (e.g., "2.4.0"){{amendment_date}} → Today's date (YYYY-MM-DD format){{amendment_type}} → MAJOR/MINOR/PATCH{{change_description}} → User input{{migration_notes}} → User input (or "N/A" for PATCH){{rationale}} → User inputRendering: Simple string replacement (no external dependencies)
Find or create changelog section:
Look for:
## Changelog
If not found, insert after preamble (before first ## principle):
## Changelog
### Version {{new_version}} - {{amendment_date}}
**Type**: {{amendment_type}}
**Changes**:
{{change_description}}
**Migration Notes**:
{{migration_notes}}
**Rationale**:
{{rationale}}
---
If found:
Insert rendered entry immediately after ## Changelog header (newest first):
## Changelog
### Version 2.4.0 - 2026-01-25
...
### Version 2.3.0 - 2026-01-20
...
Find footer (last 3 lines typically):
---
*Last amended: YYYY-MM-DD*
*Version: X.Y.Z*
Update:
Last amended: → Today's dateVersion: → New versionIf no footer exists, append:
---
*Last amended: 2026-01-25*
*Version: 2.4.0*
Automatically invoke checklist generator:
Output instruction:
Amendment complete. Now regenerating checklist to reflect updated principles...
Then instruct Claude:
Please run the constitution:checklist-generator skill to update the implementation checklist based on the amended constitution.
(Skills cannot directly invoke other skills, so this is an instruction for Claude to execute next)
Output:
✓ Constitution amended successfully
Version: 1.2.3 → 2.0.0
Type: MAJOR
Date: 2026-01-25
Changelog entry added (3 total entries)
Footer updated
Checklist regeneration requested
⚠️ MAJOR version change detected!
Review existing code for compliance with updated principles.
Migration notes:
[User's migration guidance]
No constitution found: Error with "Run constitution:writer first"
Invalid version format: Assume 1.0.0 and add warning
Changelog placement: If unclear structure, add section at end (before footer)
Empty migration notes: Use "N/A" for PATCH, require for MAJOR/MINOR
Amendment removes principles? → MAJOR
Amendment changes core requirements fundamentally? → MAJOR
Amendment adds new principles? → MINOR
Amendment expands scope? → MINOR
Amendment clarifies existing wording? → PATCH
Amendment fixes typos? → PATCH
When uncertain: Ask user to confirm type before proceeding
❌ Don't:
✅ Do: