briefing-writelisted

Wrap create_briefing_note and update_briefing_note with topic taxonomy enforcement, participants list normalization, content size pre-flight, and auto-linking of related taskIds / missionIds mentioned in the content. Use this skill whenever the user says "write briefing note", "briefing", "decision note", "create briefing", "save briefing" -- even if they don't say "briefing-write" explicitly.
vantageos-agency/vantage-peers · ★ 2 · AI & Automation · score 64

Install: claude install-skill vantageos-agency/vantage-peers

Author or update a VantagePeers briefing note with the correct topic, normalized participants, and an evidence-bound body so cross-orchestrator readers get a self-contained artifact. **Canonical source**: VantageRegistry (`get_skill_content name=briefing-write`). The local `.claude/skills/briefing-write/SKILL.md` in each workspace MUST be a byte-exact mirror of the VR canonical content. End of hand-copy — fetch from VR, do not edit locally. PRINCIPLE — A briefing note is a fleet-wide artifact. Other orchestrators (and Laurent) read it without your session context. Topic, title, participants, and proof tokens are not decorations — they are the index, the audience, and the receipt. ## WORKFLOW **Step 1 — Detect orchestrator identity** Read the first 20 lines of `CLAUDE.md` in the current workspace to determine your role (pi, sigma, eta, alpha, lambda, tau, phi, omega, zeta, ...) and instanceId. This becomes `createdBy` on the note. If unresolved, default to the orchestrator named in the workspace path. **Step 2 — Resolve mode (create vs update)** - User said "write/create/save briefing" → CREATE mode → Step 3. - User said "update briefing j<id>" or supplied a `noteId` → UPDATE mode → Step 7. **Step 3 — Select topic (taxonomy enforcement)** Topic MUST be one of: `daily`, `decision`, `postmortem`, `retrospective`, `plan`. If the user supplied a topic, validate against the taxonomy. If absent, infer from content keywords: - Keywords "decision", "verdict", "approved", "r