docs-governance
Skill40 starsChanged 4 days agoApache-2.0View on GitHub
Use when reorganizing docs, deciding documentation homes, consolidating redundant docs, updating diagrams or doc maps, or changing documentation verification policy in this repo.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- ghvinashvili/specagenttheir own version, first seen Nov 1, 2026
- CherryHQ/cherry-studiotheir own version, first seen Oct 25, 2026
- stainless-code/losslesstheir own version, first seen Oct 24, 2026
- Hexsis-LLC/skillstheir own version, first seen Oct 13, 2026
- Seekers2001/docs-governancetheir own version, first seen Oct 13, 2026
- qshanx/docs-governancetheir own version, first seen Oct 13, 2026
Used with
Projects with it also use writing-for-agents and domain-modeling.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillwriting-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Also in 3 projects that use this
GoogleSkilldomain-modeling
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- CherryHQ/cherry-studio★ 54ksame name
- clawdotnet/openclaw.net★ 535same name
- Seekers2001/docs-governance★ 320same name
- qshanx/docs-governance★ 253same name
- ghvinashvili/specagent★ 7same name
- stainless-code/lossless★ 4same name
- Hexsis-LLC/skills★ 1same name
- EraserandRain/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 repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with repo-context, frontend, backend, and repo-operations.
- Distinctive: line 13
Use the authoring contract for policy.
- Distinctive: line 60
Verify substantive claims against current source.
- Distinctive: line 71
Run affected checks, keep audit evidence ignored, and release through repo-operations.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Documentation governance
Purpose and Trigger
- Primary scope:
docs-governance-intake - Trigger on documentation structure, canonical homes, consolidation and verification.
- Avoid overlap with
repo-context,frontend,backend, andrepo-operations. Use the authoring contract for policy; use this skill to execute the change.
Coverage and Ownership
- Role:
owner - Owner family:
docs-governance
Owned repo surfaces:
docsconsent-protocol/docshushh-webapp/docs
Non-owned surfaces:
frontendbackendrepo-operationscontributor-onboarding
Do Use
- Moving, consolidating or retiring documentation and repairing its consumers.
- Reconciling source truth, module diagrams and current versus future claims.
- Updating documentation navigation and its existing verification tools.
Do Not Use
- Product implementation merely because documentation accompanies it.
- Release-policy or deployment changes owned by repo-operations.
- Broad orientation before the owning surface is known; begin with repo-context.
Read First
docs/README.mddocs/development/documentation.mddocs/architecture/README.mddocs/operations/brand-and-compatibility-contract.md
Workflow
- Inventory first-party Markdown and inspect runtime, generator and package consumers.
- Classify current guides, technical contracts, future designs, active peer work, history, and imported/generated/legal/runtime assets before changing them.
- Choose the canonical Product, Architecture, Development, Operations or Roadmap home. Keep standalone package references local and root entrypoints useful.
- Verify substantive claims against current source. One is the implemented root private agent; Kai is its finance specialist. Do not turn source evidence into deployment or installed-owner acceptance. Current chat Markdown remains in PKM.
- Lead with purpose and behavior. Retain exact commands and identifiers where readers need them for implementation, custody, recovery or provenance.
- Reconcile unique durable facts before retirement. Preserve active peer work and unresolved recovery facts. Use Git history for prior versions, not duplicate trees.
- Move links, anchors, images, manifests, inventories and generators together. Required package assets and runtime Markdown retain their existing contracts.
- Review navigation and source truth independently for cross-system migrations. Render changed diagrams and verify both valid and broken-link behavior.
- Run affected checks, keep audit evidence ignored, and release through repo-operations. Source-only downstream syncs preserve branch content and never deploy.
Handoff Rules
Route implementation to frontend/backend owners, release operations to repo-operations, and explicitly requested executive artifacts to founder-brief-curation. Ordinary product documentation has no default Founder/CTO audience. Preserve literal compatibility identifiers and the approved Hussh personal-agent identity.
Required Checks
./bin/hushh docs verify
python3 .agents/skills/docs-governance/scripts/doc_inventory.py inventory
python3 .agents/skills/docs-governance/scripts/doc_inventory.py stale-candidates
python3 .agents/skills/docs-governance/scripts/doc_inventory.py foldersDoes 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.

