Team contacts and ownership documented

Severity: Optional

New developers should know who to ask for help with different areas. This becomes more important as team size grows.

Check automatically:

# Look for team or contact documentation
find . -maxdepth 4 -type f \( -name "*team*" -o -name "*contact*" -o -name "*owner*" -o -name "*who*" \) -name "*.md" 2>/dev/null | grep -v node_modules

# Search for ownership content
grep -riE "contact|owner|ask|responsible|maintainer|point of contact|slack|team" docs/ README.md --include="*.md" 2>/dev/null | head -10

# Check for CODEOWNERS
ls -la .github/CODEOWNERS CODEOWNERS 2>/dev/null

# Look for on-call or escalation docs
grep -riE "on.call|escalat|support|help" docs/ --include="*.md" 2>/dev/null | head -5

Ask user:

• "Does a new dev know who to ask for help with different areas?"
• "Is there a CODEOWNERS file or equivalent?"
• "Are team/area owners documented somewhere?"

Pass criteria:

• Contact/ownership info exists (doc, CODEOWNERS, or team page)
• Covers key areas: frontend, backend, infra, key systems
• New dev knows where to get help without asking around

Fail criteria:

• No ownership documentation
• "Just ask in Slack" with no guidance on who/where
• CODEOWNERS exists but only for PR routing, not discoverable for questions

Note: Small teams where everyone knows everyone may not need formal ownership docs. This becomes more important at 5+ engineers.

Evidence to capture:

• Location of ownership info
• Format (CODEOWNERS, doc, wiki, Slack channel list)
• Areas covered
• Accessibility for new devs

---