# Ownership

## Resource Ownership

- Skills and scripts should have a clear maintainer because they affect multiple
  surfaces.
- Hooks require extra scrutiny because they execute code.
- Repository overlay templates should be maintained with GitHub-side behavior in
  mind.

## Change Responsibility

Whoever introduces a shared resource is responsible for documenting it,
verifying it, and proposing deprecation guidance if it later becomes obsolete.