Skip to content

rlaope/oh-my-hermes / skills/omh-meeting-brief

omh-meeting-brief

Verified

[omh] Upcoming work meeting that lacks an agenda: agenda, prompts, decisions, and record template. Use when the user says: meeting-brief, meeting brief, meeting agenda, agenda, discussion prompts, decisions needed, record template, meeting topics.

Meeting Brief

This is a Hermes-native meeting-brief workflow skill.

Why This Exists

meeting-brief exists to turn scattered context into a focused agenda, discussion prompts, decision points, and a record template without pretending the meeting already happened.

Do Not Use When

  • The user needs observed meeting minutes, decisions, or action items but has not provided notes.
  • The request is strategy synthesis without a meeting audience, agenda, or decision ceremony.
  • The follow-up is implementation work that already has accepted requirements and should become a plan or handoff.
  • The user wants minutes, scrum history or a decision log for a recurring meeting; use omh-operating-rhythm.
  • The meeting already happened, its notes or transcript are in hand, and the user wants decisions, owners, follow-ups, or tickets drawn from them; load Hermes' bundled meeting-action-items skill instead of this one.

Examples

Good example:

  • Prompt: Prepare a meeting agenda for a leadership sync on setup UX, plugin bridge defaults, and release risk.
  • Expected behavior: Prepare agenda topics, prompts, decisions needed, and a record template with unknowns marked.
  • Why: The request is preparation for a meeting and should separate prep from observed outcomes.

Bad example:

  • Prompt: meeting-brief summarize what the team decided yesterday.
  • Expected behavior: Ask for meeting notes or route to an ops/status summary with explicit evidence gaps.
  • Why: A prepared agenda cannot be treated as observed minutes or decisions.

Completion Checklist

  • The agenda, participants or audience, decisions needed, and record template are named.
  • Meeting prep, observed minutes, accepted decisions, and action ownership are separate states.
  • Missing context that would change the meeting structure is surfaced.

Recovery Notes

  • If decision topics lack known context, retain the supplied meeting goal and audience, mark the agenda tentative, and hand back discussion prompts and the decisions-needed list with its open questions.
  • If follow-up coding lacks observed decisions or an accepted plan, retain the meeting brief, mark the coding handoff unresolved, and hand back the decisions needed rather than an implementation claim.

Workflow Lane

  • Current lane: Research and company ops - research, signals, ops, and briefings.
  • If intent belongs to another lane, hand back to omh-routing or name the adjacent workflow.
  • Shared product, routing, compatibility, and evidence rules: skill_view(name='omh-routing', file_path='references/skill-common-rail.md').

When to Use

Use when Hermes should prepare a meeting agenda, discussion prompts, decision points, and a record template.

Strong routing signals: `meeting-brief`, `meeting brief`, `meeting agenda`, `agenda`, `discussion prompts`, `decisions needed`, `record template`, `meeting topics`, `회의 주제`, `회의 아젠다`, `아젠다`, `회의 준비`, `논의 질문`, `결정할 것`, `기록 템플릿`

Catalog Metadata

Category: meeting Phase: preparation Hermes role: operator Quality tier: facilitation-gated Reasoning demand: light

Quality bar:

  • Turn context into agenda topics, prompts, decisions needed, and a record template.
  • Keep prep distinct from actual meeting minutes or accepted decisions.
  • Identify missing context that would change the meeting structure.
  • Give each agenda item a time box that sums to the meeting length, an owner and an intended outcome (decide, discuss, inform); name pre-reads and who reads them; for a decision item name the decider and what each option costs; say so when a message would meet the goal.
  • Give the record template's action-item rows outcome, owner, due date, dependency, acceptance condition, and source columns, each marked unknown until the meeting record fills it.

Handoff policy:

Run meeting preparation in Hermes; only create follow-up coding handoff from observed decisions or accepted plans.

Required inputs:

  • meeting goal, date and length
  • audience
  • known context
  • decision topics and who decides

Expected outputs:

  • agenda
  • discussion prompts
  • decisions needed
  • action-item template

Artifact expectations:

  • meeting brief or record template when the wrapper captures it

Safety rules:

  • Do not claim the meeting happened from a prepared agenda.
  • Separate proposed action items from observed decisions.
  • Use a later status or decision record for actual meeting outcomes.

Runtime Evidence

Preferred harness for this skill: meeting-facilitation.

omh runtime record --skill meeting-brief --harness meeting-facilitation --status started

Record observed delegation results; otherwise return not_available or not_observed. Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.

  • Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes. Preserve workflow intent and stop conditions; verify before claiming completion. Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only. When the requested output is delivered, put any open points inside the result and end with no question or offer; only when the person asked to choose or decide and that choice is still theirs, end with one specific question about it, not a list, a generic offer, or a footer; the shared rail's Reply Language And Host Voice and Turn Ending sections hold the full rule.

Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.

Shared product, compatibility, topology, memory, harness, and execution rules: skill_view(name='omh-routing', file_path='references/skill-common-rail.md'). Load it when applicable; otherwise name an unavailable capability.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall