Bryan Gilliom (via Claude)
2f8ba0b80b
Bryan, two related requests: 1. When a topic has a real end-client agency, the skill should resolve its full identity -- not just whatever name got said in the meeting. Added as a new standing step: check the MPM Technical Reference System first (agency-roster.md, clients-and-partners.md -- cheap, already-vetted), fall back to public web research, resolve BOTH the legal entity name and the separate transit brand name distinctly (validated pattern, confirmed against MPM's own FTA filings for Oshkosh: 'City of Oshkosh, Wisconsin, dba: GO Transit'), re-host the logo as a data URI rather than hotlinking it, and capture general agency contact info. Gets its own 'End Agency' card, separate from individual attendees. 2. Pricing shown in the Oshkosh brief was correct for an internal audience, but Bryan flagged that an external-facing version must never show the end agency MPM's price to the reseller -- they aren't privy to it. Documented as a new Hard Rule, grounded directly in the Technical Reference System's own reseller-channel.md (MPM's contract of record is with the reseller, not the agency, on channel accounts) rather than invented from scratch. Doesn't change internal-meeting- brief's current behavior (it's internal by definition) -- recorded here as the binding rule for vendor-partner-brief and kickoff-brief's external-client variant, neither built yet.
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.