meeting-brief

Name: meeting-brief
Author: rlaope

61stars2forks

How to install meeting-brief?

rlaope/oh-my-hermes/meeting-brief

$npx -y skills add rlaope/oh-my-hermes --skill meeting-brief

Installs into the current project.

Summary

[omh] Hermes Meeting Brief workflow: agenda, prompts, decisions, and record template.

Files · 1

View on GitHub

SKILL.md

1	# Meeting Brief
2
3	This is a Hermes-native `meeting-brief` workflow skill.
4
5	## Why This Exists
6
7	`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.
8
9	## Do Not Use When
10
11	- The user needs observed meeting minutes, decisions, or action items but has not provided notes.
12	- The request is strategy synthesis without a meeting audience, agenda, or decision ceremony.
13	- The follow-up is implementation work that already has accepted requirements and should become a plan or handoff.
14
15	## Examples
16
17	Good example:
18
19	- Prompt: Prepare a meeting agenda for a leadership sync on setup UX, plugin bridge defaults, and release risk.
20	- Expected behavior: Prepare agenda topics, prompts, decisions needed, and a record template with unknowns marked.
21	- Why: The request is preparation for a meeting and should separate prep from observed outcomes.
22
23	Bad example:
24
25	- Prompt: meeting-brief summarize what the team decided yesterday.
26	- Expected behavior: Ask for meeting notes or route to an ops/status summary with explicit evidence gaps.
27	- Why: A prepared agenda cannot be treated as observed minutes or decisions.
28
29	## Completion Checklist
30
31	- The agenda, participants or audience, decisions needed, and record template are named.
32	- Meeting prep, observed minutes, accepted decisions, and action ownership are separate states.
33	- Missing context that would change the meeting structure is surfaced.
34
35	## Recovery Notes
36
37	- If participants, purpose, or decision owner are missing, ask for the one field that changes the agenda.
38	- If minutes or decisions were not observed, keep the output as prep rather than record.
39
40	## OMH Context Rail
41
42	- This skill is part of OMH's Hermes workflow layer, not a standalone executor.
43	- Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries.
44	- Current lane: Research and company ops (`source-finder`, `web-research`, `best-practice-research`, `autoresearch-goal`, `research-brief`, `strategy-brief`, `feedback-triage`, `research-department`, `+6 more`) - research, signals, ops, and briefings.
45	- If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill.
46	- Cross-skill context: every OMH skill: match lane; generic tool can render or execute.
47	- Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess.
48	- Coverage: Every generated workflow skill carries this rail.
49	- Normal users talk to Hermes; OMH CLI is infra.
50	- Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence.
51
52	## Use When
53
54	Use when Hermes should prepare a meeting agenda, discussion prompts, decision points, and a record template.
55
56	Strong routing signals: `meeting-brief`, `meeting brief`, `meeting agenda`, `agenda`, `discussion prompts`, `decisions needed`, `record template`, `meeting topics`, `회의 주제`, `회의 아젠다`, `아젠다`, `회의 준비`, `논의 질문`, `결정할 것`, `기록 템플릿`
57
58	## Catalog Metadata
59
60	Category: `meeting`
61	Phase: `preparation`
62	Hermes role: `operator`
63	Quality tier: `facilitation-gated`
64
65	Quality bar:
66
67	- Turn context into agenda topics, prompts, decisions needed, and a record template.
68	- Keep prep distinct from actual meeting minutes or accepted decisions.
69	- Identify missing context that would change the meeting structure.
70
71	Handoff policy:
72
73	Run meeting preparation in Hermes; only create follow-up coding handoff from observed decisions or accepted plans.
74
75	Required inputs:
76
77	- meeting goal
78	- audience
79	- known context
80	- decision topics
81
82	Expected outputs:
83
84	- agenda
85	- discussion prompts
86	- decisions needed
87	- action-item template
88
89	Artifact expectations:
90
91	- meeting brief or record template when the wrapper captures it
92
93	Safety rules:
94
95	- Do not claim the meeting happened from a prepared agenda.
96	- Separate proposed action items from observed decisions.
97	- Use a later status or decision record for actual meeting outcomes.
98
99	## Harness Discipline
100
101	- Start from the representative harness registry in `oh-my-hermes` when the workflow needs coding, research, planning, goal execution, architecture, critique, QA, or documentation lanes.
102	- Prefer richer evidence and clearer stop conditions over adding more workfl

People who liked this also viewed

6 picks

Type

meeting-brief

61stars2forks

View on GitHub

How to install meeting-brief?

rlaope/oh-my-hermes/meeting-brief

$npx -y skills add rlaope/oh-my-hermes --skill meeting-brief

Installs into the current project.

Summary

[omh] Hermes Meeting Brief workflow: agenda, prompts, decisions, and record template.

Files · 1

View on GitHub

SKILL.md

1	# Meeting Brief
2
3	This is a Hermes-native `meeting-brief` workflow skill.
4
5	## Why This Exists
6
7	`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.
8
9	## Do Not Use When
10
11	- The user needs observed meeting minutes, decisions, or action items but has not provided notes.
12	- The request is strategy synthesis without a meeting audience, agenda, or decision ceremony.
13	- The follow-up is implementation work that already has accepted requirements and should become a plan or handoff.
14
15	## Examples
16
17	Good example:
18
19	- Prompt: Prepare a meeting agenda for a leadership sync on setup UX, plugin bridge defaults, and release risk.
20	- Expected behavior: Prepare agenda topics, prompts, decisions needed, and a record template with unknowns marked.
21	- Why: The request is preparation for a meeting and should separate prep from observed outcomes.
22
23	Bad example:
24
25	- Prompt: meeting-brief summarize what the team decided yesterday.
26	- Expected behavior: Ask for meeting notes or route to an ops/status summary with explicit evidence gaps.
27	- Why: A prepared agenda cannot be treated as observed minutes or decisions.
28
29	## Completion Checklist
30
31	- The agenda, participants or audience, decisions needed, and record template are named.
32	- Meeting prep, observed minutes, accepted decisions, and action ownership are separate states.
33	- Missing context that would change the meeting structure is surfaced.
34
35	## Recovery Notes
36
37	- If participants, purpose, or decision owner are missing, ask for the one field that changes the agenda.
38	- If minutes or decisions were not observed, keep the output as prep rather than record.
39
40	## OMH Context Rail
41
42	- This skill is part of OMH's Hermes workflow layer, not a standalone executor.
43	- Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries.
44	- Current lane: Research and company ops (`source-finder`, `web-research`, `best-practice-research`, `autoresearch-goal`, `research-brief`, `strategy-brief`, `feedback-triage`, `research-department`, `+6 more`) - research, signals, ops, and briefings.
45	- If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill.
46	- Cross-skill context: every OMH skill: match lane; generic tool can render or execute.
47	- Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess.
48	- Coverage: Every generated workflow skill carries this rail.
49	- Normal users talk to Hermes; OMH CLI is infra.
50	- Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence.
51
52	## Use When
53
54	Use when Hermes should prepare a meeting agenda, discussion prompts, decision points, and a record template.
55
56	Strong routing signals: `meeting-brief`, `meeting brief`, `meeting agenda`, `agenda`, `discussion prompts`, `decisions needed`, `record template`, `meeting topics`, `회의 주제`, `회의 아젠다`, `아젠다`, `회의 준비`, `논의 질문`, `결정할 것`, `기록 템플릿`
57
58	## Catalog Metadata
59
60	Category: `meeting`
61	Phase: `preparation`
62	Hermes role: `operator`
63	Quality tier: `facilitation-gated`
64
65	Quality bar:
66
67	- Turn context into agenda topics, prompts, decisions needed, and a record template.
68	- Keep prep distinct from actual meeting minutes or accepted decisions.
69	- Identify missing context that would change the meeting structure.
70
71	Handoff policy:
72
73	Run meeting preparation in Hermes; only create follow-up coding handoff from observed decisions or accepted plans.
74
75	Required inputs:
76
77	- meeting goal
78	- audience
79	- known context
80	- decision topics
81
82	Expected outputs:
83
84	- agenda
85	- discussion prompts
86	- decisions needed
87	- action-item template
88
89	Artifact expectations:
90
91	- meeting brief or record template when the wrapper captures it
92
93	Safety rules:
94
95	- Do not claim the meeting happened from a prepared agenda.
96	- Separate proposed action items from observed decisions.
97	- Use a later status or decision record for actual meeting outcomes.
98
99	## Harness Discipline
100
101	- Start from the representative harness registry in `oh-my-hermes` when the workflow needs coding, research, planning, goal execution, architecture, critique, QA, or documentation lanes.
102	- Prefer richer evidence and clearer stop conditions over adding more workfl

People who liked this also viewed

6 picks

Type