Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Browser & automation

omh-decision-prototype

[omh] Uncertain technical choice for a spike: bounded decision prototype workflow: resolve one uncertain interaction, API, performance, or integration choice with a disposable, isolated experiment whose observed result feeds planning. Use when the user says: decision-prototype, decision prototype, prototype this uncertain choice before planning, prototype before planning, prototype the uncertain choice, run a small spike, small spike, spike solution.

rlaope · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add rlaope/oh-my-hermes --skill omh-decision-prototype

About this skill


name: "omh-decision-prototype" description: "[omh] Uncertain technical choice for a spike: bounded decision prototype workflow: resolve one uncertain interaction, API, performance, or integration choice with a disposable, isolated experiment whose observed result feeds planning. Use when the user says: decision-prototype, decision prototype, prototype this uncertain choice before planning, prototype before planning, prototype the uncertain choice, run a small spike, small spike, spike solution." metadata: hermes: tags: [workflow, oh-my-hermes, planning] category: planning phase: decision-prototype role: planner quality_tier: decision-gated

Decision Prototype

This is an OMH decision-prototype workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

Why This Exists

decision-prototype exists so one empirical uncertainty can be settled by a bounded, disposable experiment instead of endless interviewing or an experiment hidden inside production work; it records observed results apart from interpretation and feeds planning a receipt without claiming the prototype is implementation-ready.

Do Not Use When

  • $context is the explicit-only route for a repository terminology or product decision frontier (context); preference or policy decisions that behavior cannot test stay with deep-interview.
  • $context is the explicit-only route for unresolved repository terminology or project language (context); hand only an empirical decision here.
  • The decision is already made and the request is an implementation plan with acceptance criteria; use ralplan and consume the decision receipt there.
  • The user wants the feature built, reviewed, or shipped rather than one question answered; use ultrawork after an accepted plan.
  • The request is UI creation, redesign, or polish of a real surface rather than a throwaway wireframe that answers one interaction question; use frontend.
  • The request is a premium content, layout, or visual quality gate on deliverables; use design-quality-gate.
  • The uncertainty is whether customers have the problem or would adopt the solution, which needs customer evidence rather than a technical or interaction spike; use product-discovery-validation.
  • The request needs QA certification, production-readiness evidence, or a performance baseline for release; prototype results do not generalize beyond their declared fixture and environment.

Examples

Good example:

  • Prompt: Run a small spike to check whether the streaming API can hold 500 concurrent connections on one worker before we plan the migration.
  • Expected behavior: Frame one decision question with a stable id, bound the budget and scratch worktree, prepare a timing probe with exact commands and expected observations, record only observed results, and close with a decision receipt for planning.
  • Why: One empirical uncertainty blocks planning and a cheap, reversible, isolated probe can answer it without building the migration.

Bad example:

  • Prompt: decision-prototype build the whole notifications feature as a prototype and merge it if it works.
  • Expected behavior: Refuse the multi-feature scope, ask for the one decision the prototype should settle, and route accepted implementation to ralplan then ultrawork.
  • Why: A general feature build is not a bounded experiment, and a successful prototype is never promoted without a separate accepted plan.

Completion Checklist

  • Exactly one decision question with a stable decision id, alternatives, and a falsifiable hypothesis is recorded, or the request was refused with the missing question named.
  • Time, tool, file, and command budgets carry units, and the scratch directory or temporary worktree identity matches the observed workspace.
  • The artifact kind is the smallest that can answer the question, and any expansion into feature implementation was refused.
  • Execution status is one of prepared_not_observed, observed, timeout, or inconclusive; observed outputs, evidence references, interpretation, and confidence sit in separate fields.
  • Cleanup is observed before discarded is reported, and a cleanup failure is recorded distinctly.
  • The decision receipt names the supported option, rejected option, residual risk, evidence limits, and prototype-code reference permission, and no implementation handoff was prepared from it.

Recovery Notes

  • If the request spans several decisions or has no falsifiable hypothesis, HOLD and ask for or derive the single question instead of running anything.
  • If no executor, temporary worktree, browser tool, or device is available, emit the prepared handoff with exact commands and expected observations and report every result as unobserved.
  • If the observed workspace differs from the declared scratch boundary, stop before the first write and report the mismatch as a blocker.
  • If the time or command budget runs out, record timeout with whatever was observed so far and leave interpretation as unresolved questions.
  • If observations do not falsify or support the hypothesis, record inconclusive with the evidence limits rather than choosing an option.
  • If cleanup fails, keep the artifact at its last observed cleanup state, name the residual scratch identity, and never report discarded.
  • If the user asks to ship the prototype, summarize the receipt and route to ralplan; promotion needs an accepted plan and its own implementation handoff.

Use When

Use when discussion cannot settle one interaction, API, performance, or integration choice and a cheap reversible experiment can answer it before planning; refuse unbounded or multi-feature experiments and ask for or derive one falsifiable decision question.

Strong routing signals: `decision-prototype`, `$decision-prototype`, `decision prototype`, `prototype this uncertain choice before planning`, `prototype before planning`, `prototype the uncertain choice`, `run a smal
Read the complete source ↗