[Discussion] How does constitution_update_check_list work?

[jimitshah77]

memory/constitution_update_checklist.md

• Does it update automatically based on changes in project?
• Do I have to trigger it manually whenever I make changes to those files, if yes how?
• What is the workflow while updating this?
• How does it evolve?

Need more clarity on this.

[simongartz]

NOTE: the new way to run this is to execute /constitution, in the later releases the constitution_update_checklist.md is removed.

---- old way ---
It doesn't update automatically, you need to trigger it manually run the #constitution_update_checklist.md.

workflow:

1. create project with /specify
2. update the constitution.md file with your principles
3. trigger the constitution update checklist
   ... if your principles change, you update the constitution.md file and run constitution_update_checklist.md.

[ProDataNinja]

Thanks @simongartz that makes sense I assume this section would need updating to reflect your own constitution

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