speckit-constitution

A project constitution is a versioned governance document that converts high-level engineering principles into concrete rules. It serves as the central source of truth that dependent plan, spec, and task templates reference for consistent project execution.

You update a project constitution by submitting new engineering principles. The system then applies placeholder resolution and versioned amendment tracking to generate the updated governance document and propagate changes across linked files.

Yes, the system detects extension hooks during updates and preserves their execution guidance for pre and post constitution workflows. This ensures automated triggers remain functional across your spec-kit repository without manual reconfiguration.

The best way to track amendments is using versioned amendment tracking. This records every change made from principle inputs, ensuring you can audit historical governance shifts and maintain template consistency across the repository lifecycle.

If templates drift from the project constitution, propagation checks identify inconsistencies across your spec, plan, tasks, and command files. You then re-synchronize them by updating the constitution to enforce governance alignment across the repository.