Bryan: PDF needs to happen automatically, not be a manual export --
not everyone can open the HTML comfortably. This was designed back in
CW-027's Delivery Architecture discussion but never actually built into
this skill; step 7 only produced HTML.
Fixed: step 7 now generates the PDF immediately after the HTML, via
Playwright + headless Chromium (confirmed available at /opt/pw-browsers),
using page.emulate_media('print') so the PDF gets exactly the same print
CSS this skill already ships -- no separate print logic to maintain, no
relying on someone hitting Ctrl+P themselves.
Verified end-to-end before writing this into the spec: patched a real
brief with the current print CSS, rendered to PDF, confirmed correct
Letter pagination (5 pages, no blank-page artifacts) and correct
rendering of the modern CSS (color-mix, gradients, custom properties)
that simpler non-browser PDF converters often get wrong.
Step 8 (archive) updated: both HTML and PDF save to Meeting Briefs/
every time, not PDF-on-request.
Brief (CW-027)
A family of CoWork skills that generate single-file HTML briefing infographics for Message Point Media meetings — client/partner, internal, and project — on one shared MPM-branded visual component system. Originates from a bilingual template Roger Lu (Humax) shared with Bryan; reskinned entirely to MPM's brand (CW-001 / CW-028) and English-only.
Status: 1 of 6 skills built
| Skill | Status |
|---|---|
internal-meeting-brief |
Built. Real-tested 2026-09-21 against an actual APTA 2026 booth planning meeting (recap mode). |
vendor-partner-brief |
Not started |
status-update-brief |
Not started |
five-whys-brief |
Not started |
kickoff-brief (3 audience variants) |
Not started |
development-brief (software/hardware/product) |
Not started |
Full design history, the data/continuity architecture, and delivery/hosting plan (deferred to CW-029, "Brief Server") live in CW-027's Concept.md on Drive — read that before starting work on any of the remaining five skills.
Architecture in one paragraph
Each skill pulls its own facts from connected tools (Plaud, Odoo, Gmail, Google Chat)
rather than requiring hand-assembled input, maintains continuity per real-world
project/topic via a Drive folder + _topic-state.md manifest (not the ephemeral
sandbox), and renders through one shared component library
(skills/*/assets/brief-components.css, tokens sourced from CW-028) rather than
per-brief CSS. Hosting/publishing is intentionally out of scope for this repo — see
CW-029.
Known issue
The Plaud MCP connector is currently broken (times out; appears to run as a local server via Claude Desktop, not a cloud connector). The one real brief produced so far used a manually uploaded transcript as a workaround. Needs a real fix before recap mode can run unattended.