Project Governance

Establish Context

1. Read every applicable repository instruction file before inspecting or changing the project.
2. Check the worktree state and obey the project's dirty-worktree and approval rules.
3. Discover existing documentation, requirements, plans, tests, operational procedures, and project-level skills. Prefer rg --files and targeted reads.
4. Identify the project's current terminology and source-of-truth hierarchy. Preserve them unless the user approves a migration.
5. Separate reusable governance method from project-specific product facts. Never import another project's business decisions as defaults.

For a read-only review, inspect and report without editing. For a change, explain the intended scope or implementation plan before editing when repository instructions require it.

Classify Each Fact

Assign every material statement to exactly one primary authority layer: