project-governance
Skill1 starsChanged 21 days agoApache-2.0View on GitHub
Use when starting or resuming work in this repository, handing off context, or amending project rules and reviewer responsibilities.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- JusticeSc/project-governancetheir own version, first seen Nov 8, 2026
- anotb/management-consulting-plugintheir own version, first seen Nov 1, 2026
- Hu-Wentao/skillstheir own version, first seen Aug 1, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- anotb/management-consulting-plugin★ 62same name
- JusticeSc/project-governance★ 2same name
- Hu-Wentao/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- project-reviewSkill
- live-validateSkill
- project-governanceSkill
- project-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Keep established rules distinct from proposals.
- Very specific: line 27
Use .work/ for plans, reports and scratch evidence as directed by AGENTS.md.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project governance
Resolve paths from the repository root. Read AGENTS.md, .project/constitution.md
and .project/context.md, then only the scoped rules and reviewer definitions
matching the task's paths and risks. Read .project/decisions.md for amendments,
exceptions and unresolved conflicts. Check nested agent instructions when present.
Pass this context to the chosen workflow and each reviewer:
- Task, intended outcome, affected paths and exclusions.
- Constitution version, applicable rule IDs and canonical source paths.
- Relevant architecture decisions, checks, reviewers and evidence requirements.
- Open decisions and scoped exceptions, including authority and expiry.
Keep established rules distinct from proposals. Do not waive rules or treat an AI
review as human merge approval. Amend governance through the constitution's
amendment process. Keep project policy in .project/, not duplicated in skills.
For change review, read project-review.
For UI-affecting work, follow the canonical
UI review readiness procedure
when planning validation and preparing or updating a PR.
Use .work/ for plans, reports and scratch evidence as directed by AGENTS.md.
These instructions require no global installation, Claude command or particular
agent tool. An agent without skill discovery must read these files by path.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

