Bryan Gilliom (via Claude)
2209a19eb7
First test run (Oshkosh GO Transit internal kickoff, via the actual
installed skill, not Claude manually walking the SKILL.md) surfaced real,
fixable gaps. All fixed here:
1. Print CSS bug (root cause, found by Bryan): section{break-inside:
avoid-page} plus whole-table break-inside:avoid caused a 14-page,
mostly-blank PDF. Fixed: sections can split across pages now; only
cards/table-rows avoid splitting, with repeating table headers.
2. SO/PO lookup was wrongly scoped out of this brief type by default.
Wrong -- an internal kickoff about a real sale needs the SO/PO as much
as any external brief would. Scope is now by topic nature (commercial
vs. purely internal), not by brief-type name.
3. Contact-info lookup (not just name resolution) is now an explicit
standing step in attendee capture, starting from a linked SO/PO's own
Odoo contacts when one exists.
4. Added the MPM Technical Reference System (a 131-file Drive registry:
brand, platform, display tech, products, engineering, concepts, proof)
as a standing reference for part-number/product verification --
previously unknown to this skill.
5. Pulled the real run's improved _topic-state.md schema back into the
spec: confidence tags (verified/stated/open), a folder-layout header,
numbered-vs-proposed open items, a Findings/flags section. These
emerged from real use and are now documented, not one-off.
6. Meeting transcript archival (a Meeting Transcripts/ subfolder) is now
a standing step, not something that has to be asked for.
7. section-structure.md: flow and specbar are now marked validated (real
examples: Oshkosh deployment sequence, billing milestones). Added the
meeting-vs-proposed open-items badge pattern and a standard
confidentiality footer note for this brief type.
None of this was a failure of judgment in the moment -- these are gaps
between what the file said and what real use needed, now closed.
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.