constitution:amend

Constitution Amendment Skill

You are amending a project's CONSTITUTION.md with version tracking.

Goal

Update constitutional principles with semantic versioning, maintain changelog (newest first), and automatically regenerate the implementation checklist.

Workflow

1. Find Constitution & Parse Version

Search for CONSTITUTION.md:

1. Current directory
2. Parent directories
3. Git root

Parse version from footer:

*Version: X.Y.Z*

If not found: Assume 1.0.0

2. Gather Amendment Details

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?

3. Increment Version

Rules:

• MAJOR: X+1.0.0 (e.g., 2.3.1 → 3.0.0)

  • Removes principles
  • Fundamentally changes core requirements
  • Example: "Remove TDD requirement"

• MINOR: X.Y+1.0 (e.g., 2.3.1 → 2.4.0)

  • Adds new principles
  • Expands requirements
  • Example: "Add security audit requirement"

• PATCH: X.Y.Z+1 (e.g., 2.3.1 → 2.3.2)

  • Clarifies existing principles
  • Fixes typos
  • Example: "Clarify test coverage metric"

4. Render Amendment Entry

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 input

Rendering: Simple string replacement (no external dependencies)