speckit-constitution

To update project governance documentation, you provide new principle inputs to rewrite the constitution and automatically propagate changes across dependent plan, spec, tasks, and command templates. This ensures all related documentation remains perfectly aligned with the new governance rules.

Governance drift happens when core principles change but dependent templates do not. You prevent it by updating the central constitution file, which automatically validates and rewrites all linked project documentation to match the newly established governance standards.

You manage versioning by incrementing the CONSTITUTION_VERSION variable and recording ISO-formatted amendment dates automatically during the update. This tracks the history of governance changes precisely without requiring manual date entries.

Yes, if your project uses the .specify structure, the system directly targets and fills placeholder tokens within the constitution template. It then synchronizes all dependent plan, spec, tasks, and command templates to match the updated governance.

You resolve placeholder tokens by supplying concrete principle guidance interactively or as direct input. The system replaces all template placeholders with your provided values and rewrites the constitution file accordingly.

When a project constitution is updated, dependent files undergo consistency propagation. The system validates and updates all linked plan, spec, tasks, and command template references to ensure they match the new governance framework.