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 (ulw-context); preference or policy decisions that behavior cannot test stay with ulw-interview.
• $context is the explicit-only route for unresolved repository terminology or project language (ulw-context); hand only an empirical decision here.
• The decision is already made and the request is an implementation plan with acceptance criteria; use ulw-plan and consume the decision receipt there.
• The user wants the feature built, reviewed, or shipped rather than one question answered; use ulw-work 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 omh-frontend.
• The request is a premium content, layout, or visual quality gate on deliverables; use omh-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 omh-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: