# Playbook Catalog

Every row follows the rules in [CONSTITUTION.md](CONSTITUTION.md). The **Why** column is the audit trail — it says why this earned a place, not just what it does. The **Skill link** column points to a reusable Hermes skill if one exists, instead of repeating its logic here.

| Date | Context | Impact | Why | Skill link |
|------|---------|--------|-----|-------------|
| 2026-10-25 | work | Hermes drafts a plain-language release note from engineering changelog entries before each ship | Non-technical stakeholders and non-native-English readers need updates they can actually parse | plain-language — ~/.hermes/skills/plain-language/SKILL.md |
| 2026-10-25 | personal | Example entry to seed the catalog | Shows the row format for future entries | — |
| 2026-10-25 | personal | Every Sunday Hermes posts a one-line "owed this month" summary to our family Telegram channel | Replaces manual bill tracking; nothing gets missed | — |
| 2026-10-25 | work | Hermes pulls the calendar event and the last 3 doc versions, then writes a 3-bullet brief before each sync | Cuts meeting prep from 30 minutes to 5 | — |
| 2026-10-25 | family | Hermes auto-posts chore assignments to our Telegram channel every Sunday | Removes the "whose turn is it" argument; no missed weeks | — |
| 2026-10-25 | general | Rewrite any user-facing text (briefs, project pages, announcements) into plain language before sharing | Some readers do not have English as a first language; plain language keeps the message clear for everyone | `plain-language` — `~/.hermes/skills/plain-language/SKILL.md` |