skip to content

constitution_update_checklist.md Raw History Folder

Constitution Update Checklist

When amending the constitution (/memory/constitution.md), ensure all dependent documents are updated to maintain consistency.

Templates to Update

When adding/modifying ANY article:

/templates/plan-template.md - Update Constitution Check section
/templates/spec-template.md - Update if requirements/scope affected
/templates/tasks-template.md - Update if new task types needed
/.claude/commands/plan.md - Update if planning process changes
/.claude/commands/tasks.md - Update if task generation affected
/CLAUDE.md - Update runtime development guidelines

Article-specific updates:

Article I (Library-First):

Ensure templates emphasize library creation
Update CLI command examples
Add llms.txt documentation requirements

Article II (CLI Interface):

Update CLI flag requirements in templates
Add text I/O protocol reminders

Article III (Test-First):

Update test order in all templates
Emphasize TDD requirements
Add test approval gates

Article IV (Integration Testing):

List integration test triggers
Update test type priorities
Add real dependency requirements

Article V (Observability):

Add logging requirements to templates
Include multi-tier log streaming
Update performance monitoring sections

Article VI (Versioning):

Add version increment reminders
Include breaking change procedures
Update migration requirements

Article VII (Simplicity):

Update project count limits
Add pattern prohibition examples
Include YAGNI reminders

Validation Steps

Before committing constitution changes:
- All templates reference new requirements
- Examples updated to match new rules
- No contradictions between documents
After updating templates:
- Run through a sample implementation plan
- Verify all constitution requirements addressed
- Check that templates are self-contained (readable without constitution)
Version tracking:
- Update constitution version number
- Note version in template footers
- Add amendment to constitution history

Common Misses

Watch for these often-forgotten updates:

Command documentation (/commands/*.md)
Checklist items in templates
Example code/commands
Domain-specific variations (web vs mobile vs CLI)
Cross-references between documents

Template Sync Status

Last sync check: 2025-07-16

Constitution version: 2.1.1
Templates aligned: ❌ (missing versioning, observability details)

This checklist ensures the constitution's principles are consistently applied across all project documentation.

source

1# Constitution Update Checklist
2
3When amending the constitution (`/memory/constitution.md`), ensure all dependent documents are updated to maintain consistency.
4
5## Templates to Update
6
7### When adding/modifying ANY article:
8- [ ] `/templates/plan-template.md` - Update Constitution Check section
9- [ ] `/templates/spec-template.md` - Update if requirements/scope affected
10- [ ] `/templates/tasks-template.md` - Update if new task types needed
11- [ ] `/.claude/commands/plan.md` - Update if planning process changes
12- [ ] `/.claude/commands/tasks.md` - Update if task generation affected
13- [ ] `/CLAUDE.md` - Update runtime development guidelines
14
15### Article-specific updates:
16
17#### Article I (Library-First):
18- [ ] Ensure templates emphasize library creation
19- [ ] Update CLI command examples
20- [ ] Add llms.txt documentation requirements
21
22#### Article II (CLI Interface):
23- [ ] Update CLI flag requirements in templates
24- [ ] Add text I/O protocol reminders
25
26#### Article III (Test-First):
27- [ ] Update test order in all templates
28- [ ] Emphasize TDD requirements
29- [ ] Add test approval gates
30
31#### Article IV (Integration Testing):
32- [ ] List integration test triggers
33- [ ] Update test type priorities
34- [ ] Add real dependency requirements
35
36#### Article V (Observability):
37- [ ] Add logging requirements to templates
38- [ ] Include multi-tier log streaming
39- [ ] Update performance monitoring sections
40
41#### Article VI (Versioning):
42- [ ] Add version increment reminders
43- [ ] Include breaking change procedures
44- [ ] Update migration requirements
45
46#### Article VII (Simplicity):
47- [ ] Update project count limits
48- [ ] Add pattern prohibition examples
49- [ ] Include YAGNI reminders
50
51## Validation Steps
52
531. **Before committing constitution changes:**
54   - [ ] All templates reference new requirements
55   - [ ] Examples updated to match new rules
56   - [ ] No contradictions between documents
57
582. **After updating templates:**
59   - [ ] Run through a sample implementation plan
60   - [ ] Verify all constitution requirements addressed
61   - [ ] Check that templates are self-contained (readable without constitution)
62
633. **Version tracking:**
64   - [ ] Update constitution version number
65   - [ ] Note version in template footers
66   - [ ] Add amendment to constitution history
67
68## Common Misses
69
70Watch for these often-forgotten updates:
71- Command documentation (`/commands/*.md`)
72- Checklist items in templates
73- Example code/commands
74- Domain-specific variations (web vs mobile vs CLI)
75- Cross-references between documents
76
77## Template Sync Status
78
79Last sync check: 2025-07-16
80- Constitution version: 2.1.1
81- Templates aligned: ❌ (missing versioning, observability details)
82
83---
84
85*This checklist ensures the constitution's principles are consistently applied across all project documentation.*