omh-ask

# Ask This is a Hermes-native `ask` workflow skill. ## Why This Exists `ask` exists to keep `review` 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: ask: ask Claude as an external advisor to critique this plugin bridge plan before implementation. - Expected behavior: Prepare an advisor prompt, capture the response boundary, and summarize reusable critique. - Why: The user wants outside review before committing to a direction. Bad example: - Prompt: ask: 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 `ask`. - Why: The request lacks the required inputs or would overclaim work that Hermes did not observe. ## Completion Checklist - Findings or no-issue results are grounded in concrete file, artifact, command, or source evidence. - Open questions, residual risk, and missing verification are named. - Fixes or follow-up work are separate handoffs unless the user explicitly asked to implement them. ## Recovery Notes - If the reviewed target is missing, inspect the requeste...