67 lines
4.0 KiB
Markdown
67 lines
4.0 KiB
Markdown
# 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: v0.2.0 — 1 of 6 skills built, real-world tested twice
|
|
|
|
| Skill | Status |
|
|
|---|---|
|
|
| `internal-meeting-brief` | **Built and installed.** Real-tested 2026-09-21 (APTA 2026 booth planning) and 2026-09-22 (Oshkosh GO Transit internal kickoff) — the second run was the first real invocation from the actual installed skill, not Claude hand-building it, and surfaced real fixes (see Changelog). |
|
|
| `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,
|
|
the MPM Technical Reference System) 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. Every brief produces both HTML and PDF (headless
|
|
Chromium via Playwright), archives the source transcript alongside itself, and — when
|
|
a topic has a real end-client agency — resolves and embeds that agency's identity
|
|
(legal name, transit brand name, logo, contact info). Hosting/publishing is
|
|
intentionally out of scope for this repo — see CW-029.
|
|
|
|
## Changelog
|
|
|
|
- **v0.3.0** (2026-09-22) — Feedback loop: a Drive folder
|
|
(`CW-027 — Brief/Brief — Feedback Log/`, schema in `_SCHEMA.md`) that any installed
|
|
copy of any Brief skill writes to when its user has to ask for something the
|
|
skill's instructions didn't already cover — closes the gap where field usage by
|
|
people other than Bryan had no path back to plugin maintenance. Also added Echo
|
|
Memory / Goldbrain (personal Obsidian vaults some MPM staff keep) as an optional,
|
|
per-person data source.
|
|
- **v0.2.0** (2026-09-22) — First real invocation from the installed skill (Oshkosh GO
|
|
Transit kickoff) surfaced and fixed: a print-CSS bug causing blank PDF pages; SO/PO
|
|
data wrongly excluded from this brief type by default; contact-info lookup and
|
|
part-number/product verification (via the MPM Technical Reference System) added as
|
|
standing steps; the real run's improved `_topic-state.md` schema (confidence tags,
|
|
numbered-vs-proposed items, Findings/flags) folded back into the spec; meeting
|
|
transcript archival made standing; PDF made a required parallel output instead of a
|
|
manual export; end-agency identity enrichment added; a channel/pricing
|
|
confidentiality Hard Rule recorded for future external-facing brief types. Also: the
|
|
Plaud connector issue from v0.1.0 was root-caused (wrong connector + a web-URL id
|
|
missing its `of_` prefix) and fixed, and the repo's `origin` remote — which had
|
|
drifted to the stale `git.mpm.to` — was corrected to `git2.mpm.to`.
|
|
- **v0.1.0** (2026-09-21) — Initial build: `internal-meeting-brief`, canonical shared
|
|
component CSS, fixed-vs-dynamic section-structure contract. Plaud connector
|
|
non-functional at this point; brief built from a manually uploaded transcript.
|
|
|
|
## Known issues
|
|
|
|
None currently open for `internal-meeting-brief`. The Plaud connector problem from
|
|
v0.1.0 is resolved (see Changelog) — use the official `Plaud` connector only, resolve
|
|
recording ids via `list_files(query=...)`, never from a web-app URL directly.
|