Strategy Brief
This is a Hermes-native strategy-brief workflow skill.
Why This Exists
strategy-brief exists to keep strategy work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
Do Not Use When
- The strategic question is whether an early idea's customer problem and segment are real, and no validated discovery receipt exists yet; use
product-discovery-validation.
Examples
Good example:
- Prompt: strategy-brief: decide whether our onboarding should prioritize solo founders or enterprise buyers.
- Expected behavior: Frame options, tradeoffs, assumptions, rejected paths, and the decision evidence needed.
- Why: The request is strategy-shaped and should not jump directly into implementation.
Bad example:
- Prompt: strategy-brief: treat casual chat or unaccepted work as if this workflow already produced verified results.
- Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing
strategy-brief.
- Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.
Completion Checklist
- The decision, options, tradeoffs, assumptions, and rejected alternatives are named.
- Observed signals are separated from strategic inference.
- Accepted decisions and implementation follow-ups are not conflated.
Recovery Notes
- If evidence is mostly assumption, label it and recommend a research or feedback-triage pass.
- If the decision owner is missing, keep the output as options rather than accepted strategy.
Workflow Lane
- Current lane: Research and company ops (
product-docs, source-finder, web-research, research, best-practice-research, autoresearch-goal, model-optimization, inference-serving, +19 more) - research, signals, ops, and briefings.
- If intent belongs to another lane, hand back to
oh-my-hermes or name the adjacent workflow.
- Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Use When
Use when Hermes should turn goals and evidence into options, tradeoffs, recommendations, and a decision-ready brief.
Strong routing signals: `strategy-brief`, `strategy brief`, `strategy memo`, `product strategy`, `strategic options`, `decision note`, `leadership strategy`, `next strategy`, `다음 전략`, `전략 정리`, `전략 메모`, `전략 옵션`, `의사결정`, `리더십 회의`
Catalog Metadata
Category: strategy
Phase: brief
Hermes role: operator
Quality tier: decision-gated
Reasoning demand: standard
Quality bar:
- Name the decision, constraints, options, tradeoffs, and rejected alternatives.
- Tie recommendations to observed evidence or mark them as assumptions.
- Keep coding handoff disabled until strategy is accepted and code work is explicit.
- Ask whether the decision deserves a durable record - hard to reverse, surprising without its context, and carrying a real trade-off; all three or no record, a decision note in chat is enough.
- When a record is warranted, draft it per
omh-decide/references/decision-records.md - the docs/adr/ convention with Context, Drivers, Considered Options, Decision, Consequences with mitigations, and Related - and stop for the user's approval before any file is written.
- Never edit an accepted record: status moves Proposed to Accepted to Deprecated or Superseded, supersession is a new record pointing back at the old one, and a Rejected record is kept - it is what
decision-recall reads later.
Handoff policy:
Keep strategy synthesis in Hermes; do not create implementation handoff until a decision is accepted and code work is explicit.
Required inputs:
- goal
- known evidence
- constraints
- decision owner
Expected outputs:
- options
- tradeoffs
- recommended direction
- decision note
Artifact expectations:
- strategy brief or decision note when a wrapper captures it
Safety rules:
- Do not treat a draft recommendation as an accepted decision.
- Keep unresolved assumptions visible.
- Separate strategy from implementation planning unless the user asks for execution.
- A drafted decision record stays a proposal: nothing is written under
docs/adr/ until the user approves the write.
Runtime Evidence
Preferred harness for this skill: strategy-synthesis.
omh runtime record --skill strategy-brief --harness strategy-synthesis --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.
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: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.
1---
2name: "omh-decide"
3description: "[omh] Decide between options: tradeoffs, a recommendation, and a decision note you can act on. Use when the user says: strategy-brief, strategy brief, strategy memo, product strategy, strategic options, decision note, leadership strategy, next strategy."
4metadata:
5 hermes:
6 tags: [workflow, oh-my-hermes, strategy]
7 category: strategy
8 phase: brief
9 role: operator
10 quality_tier: decision-gated
11---
12
13# Strategy Brief
14
15This is a Hermes-native `strategy-brief` workflow skill.
16
17## Why This Exists
18
19`strategy-brief` exists to keep `strategy` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
20
21## Do Not Use When
22
23- The strategic question is whether an early idea's customer problem and segment are real, and no validated discovery receipt exists yet; use `product-discovery-validation`.
24
25## Examples
26
27Good example:
28
29- Prompt: strategy-brief: decide whether our onboarding should prioritize solo founders or enterprise buyers.
30- Expected behavior: Frame options, tradeoffs, assumptions, rejected paths, and the decision evidence needed.
31- Why: The request is strategy-shaped and should not jump directly into implementation.
32
33Bad example:
34
35- Prompt: strategy-brief: treat casual chat or unaccepted work as if this workflow already produced verified results.
36- Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `strategy-brief`.
37- Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.
38
39## Completion Checklist
40
41- The decision, options, tradeoffs, assumptions, and rejected alternatives are named.
42- Observed signals are separated from strategic inference.
43- Accepted decisions and implementation follow-ups are not conflated.
44
45## Recovery Notes
46
47- If evidence is mostly assumption, label it and recommend a research or feedback-triage pass.
48- If the decision owner is missing, keep the output as options rather than accepted strategy.
49
50## Workflow Lane
51
52- Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `best-practice-research`, `autoresearch-goal`, `model-optimization`, `inference-serving`, `+19 more`) - research, signals, ops, and briefings.
53- If intent belongs to another lane, hand back to `oh-my-hermes` or name the adjacent workflow.
54- Shared product, routing, compatibility, and evidence rules: `omh-routing/references/skill-common-rail.md`.
55
56## Use When
57
58Use when Hermes should turn goals and evidence into options, tradeoffs, recommendations, and a decision-ready brief.
59
60 Strong routing signals: `strategy-brief`, `strategy brief`, `strategy memo`, `product strategy`, `strategic options`, `decision note`, `leadership strategy`, `next strategy`, `다음 전략`, `전략 정리`, `전략 메모`, `전략 옵션`, `의사결정`, `리더십 회의`
61
62## Catalog Metadata
63
64Category: `strategy`
65Phase: `brief`
66Hermes role: `operator`
67Quality tier: `decision-gated`
68Reasoning demand: `standard`
69
70Quality bar:
71
72- Name the decision, constraints, options, tradeoffs, and rejected alternatives.
73- Tie recommendations to observed evidence or mark them as assumptions.
74- Keep coding handoff disabled until strategy is accepted and code work is explicit.
75- Ask whether the decision deserves a durable record - hard to reverse, surprising without its context, and carrying a real trade-off; all three or no record, a decision note in chat is enough.
76- When a record is warranted, draft it per `omh-decide/references/decision-records.md` - the `docs/adr/` convention with Context, Drivers, Considered Options, Decision, Consequences with mitigations, and Related - and stop for the user's approval before any file is written.
77- Never edit an accepted record: status moves Proposed to Accepted to Deprecated or Superseded, supersession is a new record pointing back at the old one, and a Rejected record is kept - it is what `decision-recall` reads later.
78
79Handoff policy:
80
81Keep strategy synthesis in Hermes; do not create implementation handoff until a decision is accepted and code work is explicit.
82
83Required inputs:
84
85- goal
86- known evidence
87- constraints
88- decision owner
89
90Expected outputs:
91
92- options
93- tradeoffs
94- recommended direction
95- decision note
96
97Artifact expectations:
98
99- strategy brief or decision note when a wrapper captures it
100
101Safety rules:
102
103- Do not treat a draft recommendation as an accepted decision.
104- Keep unresolved assumptions visible.
105- Separate strategy from implementation planning unless the user asks for execution.
106- A drafted decision record stays a proposal: nothing is written under `docs/adr/` until the user approves the write.
107
108## Runtime Evidence
109
110Preferred harness for this skill: `strategy-synthesis`.
111
112```sh
113omh runtime record --skill strategy-brief --harness strategy-synthesis --status started
114```
115
116Record observed delegation results; otherwise return `not_available` or `not_observed`.
117Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
118- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
119Preserve workflow intent and stop conditions; verify before claiming completion.
120
121Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
122
123Shared product, compatibility, topology, memory, harness, and execution rules: `omh-routing/references/skill-common-rail.md`. Load it when applicable; otherwise name an unavailable capability.
rlaope