omh-idea-to-deploy

# Idea To Deploy This is a Hermes-native `idea-to-deploy` workflow skill. ## Why This Exists `idea-to-deploy` exists to keep `delivery` 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: idea-to-deploy: turn this onboarding idea into a scoped plan, implementation handoff, QA gate, and release path. - Expected behavior: Prepare the idea-to-release lane while keeping implementation, QA, and deploy evidence observed-only. - Why: The request spans product shaping through deploy readiness instead of a single task. Bad example: - Prompt: idea-to-deploy: 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 `idea-to-deploy`. - Why: The request lacks the required inputs or would overclaim work that Hermes did not observe. ## Completion Checklist - Confirm the workflow target, evidence boundary, and stop condition are named. - Report which outputs are prepared, observed, blocked, or missing. - Name the smallest next verification or handoff instead of claiming completion from narration....