speckit-constitution

To update a project constitution, replace template placeholders with concrete governance rules and apply synchronized guidance. This propagates constitutional changes into planning, specification, task, and command templates so the repository stays aligned in one pass.

When a spec-kit constitution changes, downstream templates receive refreshed dependent guidance. The skill applies consistency checks across plan, spec, tasks, commands, and runtime guidance files to prevent stale placeholders and conflicting rules.

Constitution versioning discipline and amendment tracking are applied during the update process. The skill adds ratification metadata and ensures principled updates are recorded, replacing generic placeholders with dated, concrete governance decisions.

Yes, a valid .specify structure is required. The skill targets spec-kit repositories that need principled updates, relying on this existing environment to fill the constitution template with principles, governance rules, dates, and versioning decisions.

Stale placeholders remain when constitutional changes are not propagated to dependent files. This skill resolves the issue by replacing placeholders with concrete principles and refreshing downstream planning, specification, and runtime guidance templates.

The best way to draft a spec-kit constitution is to use a skill that fills the template with concrete principles, governance rules, dates, and versioning decisions. It rewrites the constitution and refreshes dependent guidance simultaneously to maintain repository consistency.