speckit-constitution

To update team governance principles in a Spec Kit repository, rewrite the constitution file by merging evidence-backed principles, generating Chinese-first review text, and tracking impacted downstream planning artifacts. This maintains stable compatibility boundaries and workflow expectations during repository evolution.

A team constitution in software engineering governance is a durable contract, typically stored as .specify/memory/constitution.md, that defines team principles, compatibility boundaries, and branch workflow decision rules. It ensures governance expectations stay consistent across project updates and downstream task routing.

To track which specs and templates need revision when governance changes, update the constitution file using evidence-backed merging and review the generated downstream artifact impact notes. This process identifies specific planning and template artifacts affected by the constitutional guidance shifts.

This governance workflow is designed specifically for Spec Kit repositories that maintain a .specify workspace. It relies on the repository's existing memory assets and task-routing structures to apply constitutional updates and generate accurate downstream artifact impact notes.

Updating the Spec Kit constitution requires explicit human review before feature workflow continuation. The process generates Chinese-first review text and next-step routing guidance, ensuring team members validate evidence-backed principle changes before any downstream tasks proceed.

The Spec Kit constitution outputs Chinese-first review text to preserve governance workflow requirements and ensure localized accessibility for teams reviewing constitutional updates. This approach maintains consistency in how branch workflow and compatibility policy decisions are documented and validated.