# Omh Decide

[omh] Team or business decision between options: tradeoffs, a recommendation, and a...

- Repository: https://github.com/rlaope/oh-my-hermes (5004 stars)
- Category: Business
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rlaope/oh-my-hermes --skill omh-decide -g -a claude-code -y`
Codex: `npx skills add rlaope/oh-my-hermes --skill omh-decide -g -a codex -y`
Cursor: `npx skills add rlaope/oh-my-hermes --skill omh-decide -g -a cursor -y`
Gemini CLI: `npx skills add rlaope/oh-my-hermes --skill omh-decide -g -a gemini-cli -y`

## Description

[omh] Team or business decision 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Strategy Brief

This is an OMH `strategy-brief` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

## 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 `omh-product-discovery-validation`.
- The question is how to run a hiring process, scorecards, interview loops, candidate comparison, rather than whether to hire at all; use `omh-people-ops`.
- The user wants Jev's typed probabilities for a yes/no, pick-one, or scored question over supplied text rather than tradeoffs and a recommendation.

## 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.



## When to Use

The rest: https://github.com/rlaope/oh-my-hermes/blob/HEAD/agent-skills/omh-decide/SKILL.md