speckit-constitution

Define project governance by establishing a project constitution that outlines non-negotiable coding standards, testing requirements, and architectural constraints. This ensures code quality and architectural consistency across the team from the outset.

A project constitution is a foundational document defining governing principles and development guidelines. You need to create one at the start of a software project to establish coding standards and architectural constraints that all team members must adhere to.

Update development guidelines by modifying existing principles within the project constitution. This process manages placeholder token replacement and ensures consistency across related project templates, including plans, specifications, and task definitions.

Yes, a constitution document enforces code quality and testing standards by defining governing principles based on user input and repository context. It establishes non-negotiable rules that all team members must follow during development.

The best way to maintain architectural consistency is to initialize core principles and rules using a project constitution. This sets foundational development guidelines and ensures all related project templates align with your architectural constraints.

Project governance principles are stored in the `.specify/memory/constitution.md` file. The constitution skill manages placeholder token replacement in this file based on your repository context to maintain documentation consistency.