New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Omh Product Brief

by rlaope in rlaope/oh-my-hermes

[omh] PRD or roadmap priorities to decide: turn product evidence into a decision-ready PRD, prioritization frame, and roadmap brief.

MITAuto-check passedProduct & Project Management

Install Omh Product Brief

skills CLI
$ npx skills add rlaope/oh-my-hermes --skill omh-product-brief -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rlaope/oh-my-hermes omh-product-brief --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omh-product-brief .claude/skills/omh-product-brief && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
omh-product-brief
GitHub stars
3.2k
Token cost
~1.7k tokens
SKILL.md length
822 words
Files
1
Skills in repo
143
Repo updated
First seen
Licence
MIT

At a glance

[omh] PRD or roadmap priorities to decide: turn product evidence into a decision-ready PRD, prioritization frame, and roadmap brief.

  • The user says: product requirements document
  • SKILL.md covers Why This Exists, Do Not Use When, Examples and Completion Checklist, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Roadmap prioritization

What it does

Omh Product Brief is an agent skill from rlaope/oh-my-hermes. [omh] PRD or roadmap priorities to decide: turn product evidence into a decision-ready PRD, prioritization frame, and roadmap brief. Use when the user says: product requirements document, PRD, roadmap prioritization, 제품 요구사항 문서, 제품 기획서, 로드맵 우선순위.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing and Prioritization frameworks. The repository describes itself as: All in one plugin for Hermes Agent ⚚ the coding intelligence, a long-term memory system and model optimized workflow packages. The licence is MIT.

When your agent uses it

  • The user says: product requirements document
  • Roadmap prioritization

Example prompts

  • “/omh-product-brief”

What it can do on your machine

Read from SKILL.md and the folder at commit 7cd0d02. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Omh Product Brief loads about 1.7k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 822 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rlaope/oh-my-hermes at commit 7cd0d02, republished under its MIT licence (© rlaope). 822 words, ~1,718 tokens.

Download SKILL.mdSave it as .claude/skills/omh-product-brief/SKILL.md (or your agent's skills folder).
name
omh-product-brief
description
[omh] PRD or roadmap priorities to decide: turn product evidence into a decision-ready PRD, prioritization frame, and roadmap brief. Use when the user says: product requirements document, PRD, roadmap prioritization, 제품 요구사항 문서, 제품 기획서, 로드맵 우선순위.

Product Brief

This is a Hermes-native product-brief workflow skill.

Why This Exists

product-brief turns product evidence into a reviewable PRD and prioritization frame before delivery planning without treating a draft as an accepted roadmap commitment.

Do Not Use When

  • The input is unprocessed feedback, bug reports, or feature asks that first need clustering and evidence boundaries; use feedback-triage.
  • The product evidence is unvalidated, synthetic, or a founder belief and the problem gate has not returned validated; use product-discovery-validation before a PRD.
  • The input is a growth hypothesis that still needs an experiment and readout before it becomes a product requirement; use lifecycle-growth.
  • The user needs a company or product strategy decision across high-level options rather than a requirements or roadmap artifact; use strategy-brief.
  • The request is an accepted, code-ready change with repository constraints and verification needs; use ralplan or ultrawork rather than recreating a PRD.
  • The user asks to create or update Jira, Linear, Aha!, or a roadmap system directly; use connector-operator with explicit target, approval, and observed evidence.

Examples

Good example:

  • Prompt: Create a PRD and prioritization options for reducing first-time user drop-off in onboarding.
  • Expected behavior: Prepare the product problem, user and metric brief, PRD, roadmap options, tradeoffs, and downstream prerequisites.
  • Why: The request needs a decision-ready requirements and prioritization artifact before delivery planning.

Bad example:

  • Prompt: Implement the accepted onboarding PRD and open a PR.
  • Expected behavior: Route to ultrawork or ralplan, not product-brief.
  • Why: Accepted implementation work should move into planning or delivery rather than recreate a PRD.

Completion Checklist

  • The plan names goals, non-goals, assumptions, acceptance criteria, and verification shape.
  • Draft recommendations, accepted decisions, and executor handoffs are separate states.
  • Rejected options or unresolved tradeoffs are recorded before handoff.

Recovery Notes

  • If acceptance criteria or verification are missing, route back to clarification before handoff.
  • If assumptions materially affect the plan, keep them visible and avoid treating the plan as accepted.

Workflow Lane

  • Current lane: Intent -> plan (oh-my-hermes, meta-router, deep-interview, context, plan, ralplan, adversarial-consensus, codebase-onboarding, +8 more) - clarify, plan, ship, or loop goals.
  • 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 a product owner needs a problem frame, user/outcome definition, PRD, prioritization/roadmap options, dependencies, acceptance shape, and decision record before delivery planning.

Strong routing signals: `product requirements document`, `PRD`, `roadmap prioritization`, `제품 요구사항 문서`, `제품 기획서`, `로드맵 우선순위`
Show full SKILL.md (421 more words)Show less

Catalog Metadata

Category: planning Phase: product-brief Hermes role: planner Quality tier: planning-gated Reasoning demand: standard

Quality bar:

  • Name problem, user, metric, goals, non-goals, requirements, dependencies, risks, and acceptance shape.
  • Preserve decision owner and downstream prerequisite boundaries.

Handoff policy:

Keep domain framing, clarification, source/evidence synthesis, draft outputs, and next-work routing in Hermes. A prepared brief, review, reply, or plan is not an external action, approval, filing, send, publish, data mutation, implementation, review, CI, or merge claim. Prepare a connector, file, coding, or human-review handoff only when the user explicitly accepts that next step; report it only from observed evidence. A PRD or roadmap is prepared planning, not stakeholder acceptance, Jira or Linear mutation, implementation, test evidence, delivery, or a market commitment.

Required inputs:

  • product evidence
  • problem and user
  • goal and non-goals
  • decision owner

Expert clarification questions:

  • product evidence
    • English: What product evidence should anchor this brief?
    • Korean: 이 브리프의 근거가 될 제품 증거는 무엇인가요?

Expected outputs:

  • problem, user, evidence, metric, goal, and non-goal brief
  • PRD with requirements, open questions, risks, dependencies, and acceptance shape
  • prioritization/roadmap options with tradeoffs and decision owner
  • explicit downstream route to ralplan, strategy-brief, or ultrawork only when its prerequisite is satisfied

Artifact expectations:

  • prepared product brief or PRD when a wrapper captures it

Safety rules:

  • Separate product evidence, assumptions, prioritization options, and stakeholder acceptance.
  • Do not claim roadmap-system mutation, implementation, test evidence, delivery, or market commitment.

Runtime Evidence

Preferred harness for this skill: planning.

sh
omh runtime record --skill product-brief --harness planning --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.

  • Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes. Preserve workflow intent and stop conditions; verify 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 stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done.

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.

© rlaope, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/omh-product-brief of rlaope/oh-my-hermes.

Open the folder on GitHubat commit 7cd0d02

Compare with similar skills

Omh Product Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Omh Product Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Omh Product Brief this skillrlaope/oh-my-hermes3.2k—~1.7kAutomated safety check: PassMIT
Product Manager Toolkitdavila7/claude-code-templates33k7 repos~2.2kAutomated safety check: PassMIT
Product Manager Toolkitmajiayu000/spellbook287—~2.2kAutomated safety check: PassMIT
Bmad Prdaj-geddes/claude-code-bmad-skills488—~1.8kAutomated safety check: NotesCustom licence
Oma Pmfirst-fluke/oh-my-agent1.3k—~1.9kAutomated safety check: PassMIT
Product Manager Toolkitsickn33/agentic-awesome-skills47k3 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Product Manager Toolkit

    davila7/claude-code-templates

    Scores feature requests with RICE, mines customer interview transcripts for pain points, and offers PRD templates, with two Python scripts behind it.

    33k GitHub starsUsed in 7 repos~2.2k tokens
    Product & Project ManagementAuto-check passed

  • Product Manager Toolkit

    majiayu000/spellbook

    Product management helpers: a RICE scoring script, an interview transcript analyzer and PRD templates for prioritizing features, synthesizing research and writing requirements.

    287 GitHub stars~2.2k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

  • Bmad Prd

    aj-geddes/claude-code-bmad-skills

    PRD facilitator (John the PM). An agent skill from aj-geddes/claude-code-bmad-skills.

    488 GitHub stars~1.8k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check: notes

  • Oma Pm

    first-fluke/oh-my-agent

    Turn product requirements into scoped tasks with dependencies and acceptance criteria.

    1.3k GitHub stars~1.9k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Product Manager Toolkit

    sickn33/agentic-awesome-skills

    Essential tools and frameworks for modern product management, from discovery to delivery.

    47k GitHub starsUsed in 3 repos~2.3k tokens
    Product & Project ManagementAuto-check passed

  • Product Management

    ooiyeefei/ccc

    This skill should be used when the user asks to "analyze my product", "research competitors", "find feature gaps", "create feature request", "prioritize backlog", "generate PRD", "plan roadmap"…

    495 GitHub stars~1.8k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed

More from rlaope/oh-my-hermes

All 143 skills in this repo

  • Omh Accessibility Audit

    rlaope/oh-my-hermes

    [omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces.

    3.3k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Omh Agent Debug

    rlaope/oh-my-hermes

    [omh] Agent is stuck, looping, or drifting: capture a stuck, looping, drifting, or repeatedly failing agent run, diagnose the likely failure pattern, and prepare the smallest safe recovery action.

    3.3k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Omh Agent Evaluation

    rlaope/oh-my-hermes

    [omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics.

    3.3k GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Omh Agent Instructions

    rlaope/oh-my-hermes

    [omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or…

    3.3k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Omh Agent Ops Review

    rlaope/oh-my-hermes

    [omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers.

    3.3k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Omh AI Slop Cleaner

    rlaope/oh-my-hermes

    [omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical.

    3.3k GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Omh Product Brief

What does Omh Product Brief do?

[omh] PRD or roadmap priorities to decide: turn product evidence into a decision-ready PRD, prioritization frame, and roadmap brief. Omh Product Brief is an agent skill from rlaope/oh-my-hermes. [omh] PRD or roadmap priorities to decide: turn product evidence into a decision-ready PRD, prioritization frame, and roadmap brief.

When should I use Omh Product Brief?

Omh Product Brief fits situations like: the user says: product requirements document; roadmap prioritization.

How do I install Omh Product Brief in Claude Code?

Run `npx skills add rlaope/oh-my-hermes --skill omh-product-brief -a claude-code`. Or copy the skill folder (skills/omh-product-brief in rlaope/oh-my-hermes) into .claude/skills/omh-product-brief in your project. Claude Code loads it when a task matches its description.

How do I install Omh Product Brief in Codex?

Run `npx skills add rlaope/oh-my-hermes --skill omh-product-brief -a codex`. Or copy the skill folder (skills/omh-product-brief in rlaope/oh-my-hermes) into .agents/skills/omh-product-brief in your project. Codex loads it when a task matches its description.

Can I use Omh Product Brief in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rlaope/oh-my-hermes --skill omh-product-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omh-product-brief, .gemini/skills/omh-product-brief, .github/skills/omh-product-brief and .opencode/skills/omh-product-brief in your project.

What does Omh Product Brief need to run?

SKILL.md names no scripts, command-line tools or credentials: Omh Product Brief is instructions for the agent only.

Does Omh Product Brief access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Omh Product Brief safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Omh Product Brief use?

Omh Product Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Omh Product Brief use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Omh Product Brief?

Skills that share tags, products or a category with Omh Product Brief: Product Manager Toolkit (davila7/claude-code-templates, 33k stars), Product Manager Toolkit (majiayu000/spellbook, 287 stars), Bmad Prd (aj-geddes/claude-code-bmad-skills, 488 stars) and Oma Pm (first-fluke/oh-my-agent, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Omh Product Brief?

rlaope (a GitHub user) maintains it in rlaope/oh-my-hermes, which has 3,243 GitHub stars. The repository holds 143 skills in this directory. The repository was last updated on October 10, 2026.

Source: rlaope/oh-my-hermes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.