speckit-constitution

To update project constitution templates, the skill detects `[ALL_CAPS_IDENTIFIER]` tags in `.specify/memory/constitution.md` and fills them using user input or inferred repository data. It resolves placeholders to ensure your governance file reflects current principles.

Semantic versioning for spec-kit governance files determines the appropriate version bump (major, minor, or patch) based on principle changes. It automatically updates ratification and amendment dates when the constitution is modified.

Yes, you need a `.specify` directory containing memory and template files. This skill is applied to spec-kit projects that already have this structure in place to read and update the constitution correctly.

Yes, you can propagate governance changes across related spec-kit templates. The skill scans plan, spec, tasks, and command files to ensure they reflect the updated principles from your constitution automatically.

To track compliance impacts when amending a project constitution, the skill generates an HTML-comment summary. This impact report details applied changes, required updates, and TODO items across your spec-kit project.

The best way to keep spec-kit constitution files consistent is using automated placeholder resolution, semantic version bumps, and consistency propagation across related templates. This eliminates error-prone manual edits.