speckit-constitution

To automate constitution updates, the skill derives concrete values from user input or repository context to fill the .specify/memory/constitution.md file and propagates amendments across dependent artifacts automatically, reducing manual drift in governance documents.

The versioning policy for amending a project constitution enforces formal MAJOR, MINOR, and PATCH version increments. It records ratification and amendment dates with clear rationale to maintain strict governance compliance and historical tracking.

To ensure consistency across governance templates, the skill validates alignment with related plan-template.md, spec-template.md, and tasks-template.md files alongside guidance docs, enforcing placeholder replacement and consistency checks throughout the .specify directory.

Yes, you can use this skill to fill placeholders without manual input because it can derive concrete values directly from your repository context to resolve placeholders in the constitution.md file and propagate changes across dependent artifacts.

The best way to keep your project constitution in sync is to apply automated consistency checks and versioning policies. This skill updates the constitution to reflect current governance principles, resolves placeholders, and increments versions correctly across amendments.