Ownership Chain Skill

Code without an owner is a liability. When it breaks at 2am, nobody knows who to wake up. When it needs to change, nobody knows who to ask for context. When it needs to be deleted, nobody knows if it is safe to remove.

AI agents create code without owners by default. This skill fixes that.

What Ownership Requires

Every new service, module, background job, API endpoint group, or significant feature must have three things declared before it ships:

1. A team owner Who is responsible for this code? Not a person's name. A team name that survives personnel changes. If no team owns it, it does not ship until someone claims it.

2. A runbook Where is the document that tells an on-call engineer what to do when this breaks? This can be a stub — a file that exists with headings but not yet filled in — but it must exist and be linked.

3. An on-call rotation Which rotation gets paged when this code fails? If no rotation covers it, that is a gap that must be named and resolved, not silently accepted.