idea-to-deploy
starsforks
How to install idea-to-deploy?
rlaope/oh-my-hermes/idea-to-deploy
$npx -y skills add rlaope/oh-my-hermes --skill idea-to-deploy[omh] Hermes Idea-to-Deploy workflow: shape an app idea into decisions, delivery handoff, verification, release, and monitoring status.
SKILL.md
| 1 | # Idea To Deploy |
| 2 | |
| 3 | This is a Hermes-native `idea-to-deploy` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `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. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence. |
| 12 | - The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed. |
| 13 | |
| 14 | ## Examples |
| 15 | |
| 16 | Good example: |
| 17 | |
| 18 | - Prompt: idea-to-deploy: turn this onboarding idea into a scoped plan, implementation handoff, QA gate, and release path. |
| 19 | - Expected behavior: Prepare the idea-to-release lane while keeping implementation, QA, and deploy evidence observed-only. |
| 20 | - Why: The request spans product shaping through deploy readiness instead of a single task. |
| 21 | |
| 22 | Bad example: |
| 23 | |
| 24 | - Prompt: idea-to-deploy: treat casual chat or unaccepted work as if this workflow already produced verified results. |
| 25 | - Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `idea-to-deploy`. |
| 26 | - Why: The request lacks the required inputs or would overclaim work that Hermes did not observe. |
| 27 | |
| 28 | ## Completion Checklist |
| 29 | |
| 30 | - Confirm the workflow target, evidence boundary, and stop condition are named. |
| 31 | - Report which outputs are prepared, observed, blocked, or missing. |
| 32 | - Name the smallest next verification or handoff instead of claiming completion from narration. |
| 33 | |
| 34 | ## Recovery Notes |
| 35 | |
| 36 | - If required context is missing, ask one blocking question or route back to the narrower workflow. |
| 37 | - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action. |
| 38 | |
| 39 | ## OMH Context Rail |
| 40 | |
| 41 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 42 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 43 | - Current lane: **Coding handoff** (`idea-to-deploy`, `cto-loop`, `deploy-and-monitor`, `code-review`, `build-failure-triage`, `verification-gate`, `security-safety-review`, `ultrawork`, `+7 more`) - coding owners, handoffs, review, CI, and merge evidence. |
| 44 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 45 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 46 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 47 | - Coverage: Every generated workflow skill carries this rail. |
| 48 | - Normal users talk to Hermes; OMH CLI is infra. |
| 49 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 50 | |
| 51 | ## Use When |
| 52 | |
| 53 | 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. |
| 54 | |
| 55 | 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`, `완제품 루프`, `아이디어부터 배포`, `기획부터 배포`, `출시까지`, `앱 운영 루프` |
| 56 | |
| 57 | ## Catalog Metadata |
| 58 | |
| 59 | Category: `delivery` |
| 60 | Phase: `app-delivery-loop` |
| 61 | Hermes role: `operator` |
| 62 | Quality tier: `delivery-gated` |
| 63 | |
| 64 | Quality bar: |
| 65 | |
| 66 | - Name the idea, user value, decision owner, non-goals, and success metric before planning delivery. |
| 67 | - Expose idea, decision, plan, handoff, verification, release, deploy, and monitor stages as separate status steps. |
| 68 | - Prepare coding handoffs only after plan acceptance and selected executor/runtime choice. |
| 69 | - Mark deploy, monitoring, and rollback as unobserved until the wrapper or operator records evidence. |
| 70 | |
| 71 | Handoff policy: |
| 72 | |
| 73 | 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. |
| 74 | |
| 75 | Required inputs: |
| 76 | |
| 77 | - product idea |
| 78 | - target user or customer signal |
| 79 | - success metric |
| 80 | - repo or app context |
| 81 | |
| 82 | Expected outputs: |
| 83 | |
| 84 | - stage rail |
| 85 | - decision gates |
| 86 | - executor handoff crit |
People who liked this also viewed
6 picksType
- microsoft-foundryDeploy, evaluate, fine-tune, and manage Foundry agents end-to-end with azd: hosted agent scaffold/run/deploy, prompt agent create, batch eval, continuous eval, prompt optimizer, Agent Optimizer scaffoSkillsJul 2026
- azure-deployExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application SkillsJul 2026
- azure-preparePrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wSkillsJul 2026
- azure-validate--- name: azure-validate description: "Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity pSkillsJul 2026
- azure-aigatewayConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: semantic caching, token limit, content safety, load balancing, AI model governance, MCP rate limiting, jailbSkillsJul 2026
- azure-hosted-copilot-sdkOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026
