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 omh-feedback-triage.
• The product evidence is unvalidated, synthetic, or a founder belief rather than external-human or behavioral-data evidence from the target segment (usage data, support contacts and interviews count); use omh-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 omh-lifecycle-growth.
• The user needs a company or product strategy decision across high-level options rather than a requirements or roadmap artifact; use omh-decide.
• The request is an accepted, code-ready change with repository constraints and verification needs; use ulw-plan or ulw-work rather than recreating a PRD.
• The user asks to create or update Jira, Linear, Aha!, or a roadmap system directly; use omh-apps with explicit target, approval, and observed evidence.

Examples