omh-decide

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