speckit-constitution

To update project governance principles, you provide interactive input or predefined values to fill placeholders in a constitution template, which then automatically syncs and propagates changes across all related project templates to ensure compliance.

Template-driven architecture for project constitution management uses a central set of principles to automatically update dependent artifacts like plans, specifications, and tasks, ensuring consistent governance enforcement across the entire project structure.

Yes, project constitution synchronization requires a `.specify/` directory within your project structure. This directory must contain the constitution file and all related template files needed for governance alignment and propagation.

Yes, you can apply predefined principles to update a project constitution. The system collects or derives values for these principles and fills in the placeholders within the constitution template without requiring manual interactive input.

The best way to ensure governance alignment is to use template synchronization, which automatically propagates constitution changes to dependent artifacts including plans, specifications, tasks, and command files, maintaining consistent adherence to policies.

Template synchronization for project governance files fails when the required `.specify/` directory is missing or does not contain the necessary constitution and related template files needed to propagate updates and enforce compliance.