speckit-constitution

To establish project governance, use a constitution document to define core principles, coding standards, and development guidelines. This ensures alignment and quality across the repository from the outset by maintaining consistent specification artifacts.

Managing project specifications involves updating a central governing constitution document. This process resolves placeholder tokens using repository context, ensuring semantic consistency and alignment across all related plan, spec, and task templates automatically.

A project constitution is a governing document that defines core principles and development guidelines. You need one when starting a new project or updating governance to ensure clear, consistent alignment and quality across all specification artifacts.

Updating a governing constitution file involves resolving placeholder tokens with user input or repository context. The process enforces semantic versioning for all updates and generates a sync impact report to maintain consistency across specification templates.

Yes, you can automatically fill template tokens with context-derived values. The system resolves placeholder tokens using user input and repository context, ensuring that project guidelines are populated accurately and consistently across artifacts.

Yes, updating project governance guidelines generates a sync impact report. This report tracks changes made to the constitution document and ensures that semantic versioning is enforced and consistency is propagated across project specification templates.