commslisted

# Comms Your communication deliverables, produced to one standard so each is fast to make and consistent to read. A deliverable is a dated folder `<briefings-dir>/<YYYY-MM-DD>-<slug>/` holding the deck source, exported deck, optional audio, and a `sources.md` provenance file. `<briefings-dir>` is `_meta/briefings/` when the repo already has a `_meta/` tree (the mise-en-place standard), else `briefings/` at the repo root — never create `_meta/` for this. A `briefings_dir` key in `.claude/comms.local.md` overrides the auto-detect (precedence below); `deliver.py briefings-dir <dir>` prints what actually resolves. The shared machinery lives in **`references/comm-package-standard.md`** (read it first). Each comm type has a self-contained playbook + a real worked example in **`examples/<type>/`**. ## Which comm (decision table) | If you want | Comm type | Toolchain | Audio | Playbook | | --- | --- | --- | --- | --- | | the decision for today | morning briefing | `deliver.py` (type `morning-briefing`) | yes (2-3 min) | `examples/morning-briefing/playbook.md` | | to close today, tee up tomorrow | end-of-day wrap-up | `deliver.py` (light) | optional | `examples/end-of-day-wrapup/playbook.md` | | the week's plan + where we stand | weekly planning briefing | `deliver.py` | yes (3-4 min) | `examples/weekly-planning/playbook.md` | | a board status readout + the ask | advisor board readout | presentations | optional | `examples/advisor-board-readout/playbook.md` | | what a client gets