What problem does it solve? Teams working with AI coding agents need persistent, repo-specific governing principles that every later workflow phase and agent inherits, but maintaining, versioning, and propagating those rules into agent context files is manual and error-prone. ## Core Features & Use Cases - Two-tier constitution management: Reads the read-only tier-1 base constitution and creates or amends the tier-2 per-repo overlay, with tier-2 taking precedence. - Versioning and Sync Impact Report: Bumps the semver version line and records what changed and what it propagates to on every amendment. - Deterministic context propagation: Pipes a pointer block through the DoFlow sync-context verb so CLAUDE.md or AGENTS.md reflects the active constitution without rewriting the whole file. - Use Case: A team lead says "amend our constitution to require integration tests for all public APIs" — the skill amends the tier-2 file, bumps the version, writes the Sync Impact Report, and updates the agent context pointer. ## Quick Start Ask the agent to set ground rules for this repository, for example: run /do-constitution with the principle that all database migrations must be reversible.
