Skip to content
cccskills
FreePublished on GitHub

omh-product-discovery-validation

Evaluate an early product idea before investing in development. Organize customer evidence, interview plans, and hypothesis tests to support a decision to stop, change direction, continue, or acknowledge that the evidence remains inconclusive.

OriginalShow the original description

[omh] Unvalidated early product idea: test whether a customer problem, segment, and business hypothesis deserve product investment, ending in kill, pivot, persevere, or inconclusive before any PRD. Use when the user says: product-discovery-validation, product discovery validation, product discovery, customer discovery, customer discovery plan, zero to one validation, validate the problem before building, problem solution interview.

Run score Not tested

See how to install

Good for

  • Validate a customer problem before building
  • Plan customer discovery interviews
  • Assess whether to continue investing in a product idea
  • Organize tests for a business hypothesis

Files included (3)

  • SKILL.md2.9 KB
  • references/full-contract.md7.2 KB
  • references/procedure.md10.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Product Discovery Validation

Required: problem, segment/evidence, owner, learning budget, and criteria. Output: a decision frame, evidence and customer plan, test portfolio, receipt, and GTM hypothesis.

HOLD: Missing inputs or failed contract gates. Prepared OMH routing is not execution or approval. Completion: Follow the full-contract checklist.

Shared product, routing, compatibility, and evidence rules: skill_view(name='omh-routing', file_path='references/skill-common-rail.md').

Agent/operator: omh runtime workflow-artifact product-discovery-validation build --input <json-file-or-> builds bounded metadata only. Shared operator reference: skill_view(name='omh-routing', file_path='references/workflow-artifacts.md').

Contract: references/full-contract.md. Procedure: references/procedure.md.

Completion Checklist

  • Preserve workflow intent and stop conditions; load the full contract before claiming completion.
  • Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a real unresolved user decision or a useful briefing discussion remains, offer one specific, content-linked question. Completed work needs no question; omit unrelated non-action footers and generic offers to continue.
  • Record observed delegation results; otherwise return not_available or not_observed.
  • Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.

Recovery Notes

  • If a required input, authority, or runtime capability is unavailable, HOLD and name the smallest safe next action; do not invent observation or approval.

Workflow Lane

advisory local context

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

dag-ulw

FreeSummary

Coordinate a large job by splitting it into small tasks with explicit dependencies. Run ready tasks in parallel through Hermes, verify the combined result separately, and repair failures within defined limits before reporting completed work and remaining gaps.

  • Delivering a feature across multiple modules
  • Coordinating a migration with ordered steps
  • Managing a broad cleanup across separate work areas
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

model-onboarding

FreeSummary

Guide the addition of a new model generation to oh-my-hermes. The workflow checks model recognition, official specifications, routing rules that select models for tasks, documented pricing, and live access, then validates changes with tests and comparative benchmarks.

  • Add a new model generation to oh-my-hermes
  • Check API model IDs and dated snapshot recognition
  • Update model selection chains and related documentation
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

Prepare an accessibility audit for an interface using WCAG 2.2 AA, an accessibility standard. Organize evidence for keyboard use, screen readers, contrast, target size, and zoom behavior, then document findings, missing checks, and remediation handoffs.

  • Reviewing checkout accessibility against WCAG 2.2 AA
  • Checking keyboard access and focus order
  • Organizing screen-reader labels and announcement evidence
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

omh-achievements

FreeSummary

Summarize earned badges, recent unlocks, achievement tiers, and progress using local files from the hermes-achievements plugin. Prepare a badge list or report section while making missing information and the limits of the recorded snapshot clear.

  • Checking earned badges
  • Reviewing recently unlocked achievements
  • Finding progress toward the next achievement tier
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

Examine a technical proposal through independent perspectives, challenge their findings, and resolve objections. The result is a structured set of constraints, decisions, risks, and open questions for a separate planning workflow.

  • Reviewing a technical proposal before planning
  • Challenging assumptions behind a migration
  • Organizing risks and unresolved questions
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

omh-agent-board

FreeSummary

Coordinate multiple Hermes agents or profiles through a shared task board. Organize assignments, handoffs, activity updates, blockers, and completion states, while distinguishing planned actions from work supported by observed results.

  • Coordinate agent roles for a launch checklist
  • Track task handoffs and blockers
  • Prepare work for pickup across profiles or after a restart
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

See all skills by rlaope

Report a problem with this skill