Strategy Brief

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

Why This Exists

strategy-brief exists so a team decision ends as a recommendation whose options are priced in one unit with their lag (and, when hard to reverse, a proposed ADR), not a discussion where each option is argued in different terms.

Do Not Use When

• A technical choice one cheap experiment can settle; use omh-decision-prototype. A technical choice inside a plan being written; use omh-plan. A technical choice the user wants attacked; use omh-adversarial-consensus. Use this skill for the decision note and ADR once the options are known.
• 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; use omh-jev-ask.

Examples

Good example: