Scenario

Leaders juggle **code quality, decision records, meetings, and escalations**. Every skill stands alone; this page is only a compass.

Suggested path (optional)

**PR culture:** Normalize `code_review` + `pr_description` snippets in your CONTRIBUTING guide.

**Architecture debates:** Use `technical_decision_record` before long meetings.

**Cross-team syncs:** Capture actions with `meeting_notes` after calls.

**Long-lived blockers:** Prefer structured `escalation_email` over chat pings.

If your process is mature, treat OpenSkill as **checklists and phrasing**—no need to replace existing tooling.