omh-idea-to-deploy

---

name: omh-idea-to-deploy description: [omh] Hermes Idea-to-Deploy workflow: shape an app idea into decisions, delivery handoff, verification, release, and monitoring status. Use when the user says: idea-to-deploy, idea to deploy, from idea to deploy, plan to deploy, idea to launch, ship this idea, ship this feature, launch this feature. metadata: hermes: tags: [workflow, oh-my-hermes, delivery] category: delivery phase: app-delivery-loop role: operator quality_tier: delivery-gated

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 task is already a concrete repo change whose stopping point is one PR-ready cycle, not product or release operations; use ultrawork.
• The request is a settings-only change, one bounded edit that is explicitly low-risk and has a direct owner and verification path, or a direct answer/diagnosis; handle it directly instead of opening a product delivery loop.

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.

Recovery Notes

• If required context is missing, ask one blocking question or route back to the narrower workflow.
• If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.

Workflow Lane

• Current lane: Coding handoff (idea-to-deploy, cto-loop, deploy-and-monitor, code-review, build-failure-triage, verification-gate, security-safety-review, ultrawork, +6 more) - coding owners, handoffs, review, CI, and merge evidence.
• If intent belongs to another lane, hand back to oh-my-hermes or name the adjacent workflow.
• Shared product, routing, compatibility, and evidence rules: omh-routing/references/skill-common-rail.md.

Use When

Use when Hermes should carry a product or app idea through shaping, decision gates, plan acceptance, executor handoff, verification, release readiness, deploy, and monitoring boundaries.

Strong routing signals: `idea-to-deploy`, `idea to deploy`, `from idea to deploy`, `plan to deploy`, `idea to launch`, `ship this idea`, `ship this feature`, `launch this feature`, `product delivery loop`, `app delivery loop`, `complete product loop`, `end-to-end app operation`, `완제품 루프`, `아이디어부터 배포`, `기획부터 배포`, `출시까지`, `앱 운영 루프`, `서비스로 만들어서 배포`, `아이디어를 서비스로`, `배포까지 가보자`, `ship this idea to production`

Catalog Metadata

Category: delivery Phase: app-delivery-loop Hermes role: operator Quality tier: delivery-gated Reasoning demand: heavy

Quality bar:

• Name the idea, user value, decision owner, non-goals, and success metric before planning delivery.
• Expose idea, decision, plan, handoff, verification, release, deploy, and monitor stages as separate status steps.
• Prepare coding handoffs only after plan acceptance and selected executor/runtime choice.
• Mark deploy, monitoring, and rollback as unobserved until the wrapper or operator records evidence.

Handoff policy:

Keep idea shaping, decision gates, planning, release narration, and status in Hermes; prepare selected executor/runtime handoffs only for accepted code work and record deploy/monitoring only from observed operator or wrapper evidence.

Required inputs:

• product idea
• target user or customer signal
• success metric
• repo or app context

Expected outputs:

• stage rail
• decision gates
• executor handoff criteria
• verification and deploy/monitor status boundaries

Artifact expectations:

• app delivery loop status record when the wrapper captures stage acceptance or observations

Safety rules:

• Do not claim implementation, deploy, health checks, rollback, or monitoring happened from a prepared loop.
• Keep coding, release, and monitoring observations as separate evidence gates.
• Ask for missing success metric, release scope, or executor choice before preparing a handoff.

Runtime Evidence

Preferred harness for this skill: app-delivery-loop.

omh runtime record --skill idea-to-deploy --harness app-delivery-loop --status started

Record observed delegation results; otherwise return not_available or not_observed. Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.

• When wrapper metadata includes memory_review_card/v1 or handoff_context_pack/v1, treat it as reviewed OMH-local or wrapper-supplied context only. Use conflict-free context summaries to shape plans and handoffs, but do not claim Hermes internal memory was read or changed. Preserve workflow intent and stop conditions; verify before claiming completion.

Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.

Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.