hf-product-discovery

Structure fuzzy product problems into a reviewable discovery draft with JTBD and OST.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hujianbest/garage-agent --skill hf-product-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf-product-discovery
Source: https://github.com/hujianbest/garage-agent/tree/main/packs/coding/skills/hf-product-discovery
Command: npx skills add https://github.com/hujianbest/garage-agent --skill hf-product-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

这项技能帮助团队将模糊的产品问题、目标用户与评审焦点收敛成可评审的 discovery 草稿,明确问题、用户、wedge、关键假设,以及进入 formal spec 前需验证的事项,避免直接进入规格设计。

Core Features & Use Cases

  • 将问题陈述、用户情境、Why now、以及 OST/Opportunity/Solutions 的骨架结构化成一个易于审阅的草稿。
  • 将“已确认事实”、“尚未确认假设”和“later ideas”清晰分层,便于后续的 hf-discovery-review 与 HF-spec 对接。
  • 提供 Bridge to Spec 的导引,帮助将稳定结论带入后续的 hf-specify。

Quick Start

Provide initial problem framing and context to begin drafting the discovery document.

Frequently Asked Questions about hf-product-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn fuzzy product ideas into a reviewable discovery draft?

To turn fuzzy ideas into a discovery draft, apply JTBD and OST frameworks to structure problem statements, user scenarios, and validation probes, ensuring confirmed facts and assumptions are clearly separated before formal spec.

What is the best way to structure product discovery before writing a formal spec?

The best way to structure product discovery is by using a structured draft that separates confirmed facts, unvalidated assumptions, and later ideas, applying JTBD and OST to clarify the problem, user, and wedge before entering formal spec.

How do I identify and validate key assumptions during product discovery?

You identify and validate key assumptions by applying validation probes within the discovery draft, maintaining strict separation between confirmed facts and assumptions to clarify the problem, user, and wedge before formal spec.

When should I use JTBD and OST frameworks in the product discovery workflow?

Use JTBD and OST frameworks in the product discovery workflow when you need to converge fuzzy product problems into a reviewable draft, clarifying the problem, user, and wedge before handing off to formal spec.

How do I transition a discovery draft into a formal specification?

To transition a discovery draft into a formal specification, use a Bridge to Spec guide to carry stable conclusions and validated facts forward, ensuring the problem, user, and wedge are fully clarified before formal spec design.