| name | repository-governance |
| description | Define and maintain repository governance for decision rights, maintainers, contribution policy, security reporting, conduct, deprecation, releases, and conflict resolution. |
Repository Governance
Use when this procedure is the primary professional method needed for the assignment.
Procedure
- Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
- Establish the evidence baseline using licenses, maintainer roster, contribution workflow, security policy, release process, and project goals. Do not fill material gaps with assumptions when they can change the result.
- Map current authority and obligations, document decision paths, separate technical review from governance decisions, establish escalation, and version policy changes.
- Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
- Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
- Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.
Quality gate
Contributors can tell who decides what, how decisions are made, and how to appeal or escalate safely.