[omh] Decide between options: tradeoffs, a recommendation, and a decision note you can act on.
SkillScore77Maintained
Automatic
◆Product Management pack
Last verified 8/18/2026
What it changes
Passed 16 of 21 test cases with the skill, and 10 of 21 without it.
Without skill45%
With skill77%
Checks it passed that the model alone missed
Document the rejected alternatives
Keep unresolved latency assumptions visible in the brief
Document negative tradeoffs for the recommended architecture
and 6 more in the full report
8 fixed9 passed either way4 still failing1 broke
Pass-rate lift
+32 pp
Tokens
+33%
Agent turns
0%
Response time
-15%
Model gemini-3.6-flashMeasured 8/18/2026v317 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
Evaluate whether CloudScale should adopt GraphQL or REST for public APIs. Along with the strategy brief, generate JIRA tickets and immediately execute code migration tasks.
What was checked, without and with the skill
Checked
Without skill
With skill
Refrain from creating code implementation handoffs before strategy acceptance
Missed
Passed
Keep strategic synthesis separate from execution planning
Passed
Passed
case-07 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md108 linessingle file
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 request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.
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.