'product-discovery' 검색 결과

Runs an iterative, conversational product-discovery process with a founder/stakeholder: structured interview, live low-fi wireframing, a linked feature/page node-graph built up as you go, a founder-confirmed lock-in checkpoint, then a generated PRD, a Mermaid-rendered sitemap, and a mockup with a full design system (palette, typography, dark mode). Use when building or operating an AI product-discovery chatbot, or when running founder/stakeholder discovery by hand and you need the structure (interview script, node-graph schema, PRD template, design-system handoff order). NOT for implementing the spec'd product once locked — hand off to feature-specific skills (ideal-web-app-builder, tailwind-v4-expert, color-theory-palette-harmony-expert, typography-expert, dark-mode-design-expert) for that. NOT for one-shot PRD generation without an interview loop — if the founder already has a written spec, this process is unnecessary overhead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Product Discovery through an 18-task methodology in 6 blocks — from market analysis to an investor-ready financial plan. Use when someone wants to run Product Discovery, validate a startup, assess a market hypothesis, prepare for an investment round, or raises an adjacent topic — idea validation, niche sizing, competitor teardown, product-market fit, pitch preparation, startup unit economics, geographic expansion into a new country, go-to-market for SEA / Asia / MENA. People rarely name PD explicitly; they say 'is there a market for this', 'assess my idea', 'I need a deck for an angel', 'we are entering Thailand/Singapore/UAE, how do we size it'. Use the skill in those cases too. Three modes: Light (~45 min, idea stage), Full (~2-3 h, MVP with customers), Geographic Expansion (~2 h, product entering a new geography). Produces 3-4 artifacts in /mnt/user-data/outputs/: one-pager.pptx, financial-plan.xlsx, presentation.pptx, optionally interview-guide.docx.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan user research by matching methods to study goals and explaining participant numbers and confidence. Synthesize tagged observations into recurring findings, distinguish isolated anecdotes, and organize evidence so research results can be found and reused.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose a research method for a study goal
• Explain participant numbers and confidence
• Find recurring patterns across participants

Evaluate product ideas before committing development resources. Organize customer needs, rank uncertain assumptions, and plan interviews or prototype tests in a short discovery cycle that ends with evidence for proceeding, changing direction, or stopping.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Mapping customer needs to solution ideas and experiments
• Prioritizing risky assumptions for testing
• Planning customer interviews and prototype tests

Finds out whether a problem is real and a solution would work, before building it — recruiting the right people, interviewing without leading them, separating what users say from what they do, naming the riskiest assumption and testing that one first, and reaching a decision rather than a summary. Use this to validate a problem, test an idea cheaply, decide whether to build something, or fix a discovery process that keeps confirming what the team already believed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create or update a product-discovery SPEC (requirements doc) for user review. Use when turning RESEARCH findings plus user intent into a reviewable requirements artifact before INNOVATE/PLAN.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Product discovery and market research expert. Use when validating product ideas, conducting market research, user interviews, competitive analysis, or opportunity assessment. Covers JTBD, Kano model, and Value Proposition Canvas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Search and filter TikTok global e-commerce products based on FastMoss data, supporting keyword search, multi-dimensional filtering (category, shop type, commission rate, sales, creator count, etc.) and sorting. Trigger when users mention TikTok product selection, TikTok product search, TikTok product data, TikTok creator sales, TikTok commission rate, TikTok bestseller tracking, TikTok GMV analysis, TikTok product search, TikTok product research, TikTok creator sales, TikTok commission rate, TikTok GMV analysis, FastMoss. Even if the user does not explicitly mention "FastMoss", trigger this skill whenever their need involves searching product data or analyzing product performance on TikTok.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Amazon product discovery and potential bestseller mining via Nexscope data. Triggered when users mention product mining, potential bestsellers, high-conversion product selection, click growth analysis, market growth opportunities, keyword-based product selection, FBA profit screening, niche market product discovery, seller origin filtering, Nexscope data, FBA profitability screening, keyword-based product selection. Even if users do not explicitly mention "Nexscope", this skill should be triggered whenever the task involves keyword-driven Amazon product selection based on conversion rates, click volume, and profitability metrics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert product discovery guidance for user research and problem validation. Use when conducting user interviews, validating problems, applying jobs-to-be-done framework, sizing opportunities, customer segmentation, competitive analysis, prototype testing, usability testing, designing surveys, or synthesizing research insights. Covers discovery sprints, continuous discovery, and research operations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

プロダクトの基盤情報（課題仮説・ソリューション・市場スコープ・原体験・ビジネスモデル・競合・差別化）を ユーザーとの対話で掘り下げ、構造化されたドキュメント（product-context.md）として整理するスキル。 「自分のプロダクトって結局何なの？」を一緒に整理する壁打ち相手として機能する。 ペルソナ作成、LP設計、機能優先順位、マーケティング戦略など、 プロダクトの方向性に関わるあらゆる意思決定の「前提情報」を1ファイルにまとめる。 コードベースがあれば自動で読み取れる部分は埋め、残りをユーザーにヒアリングする。 Use when: 「プロダクトを整理したい」「ターゲット整理」「コンテキスト作成」 「ペルソナの前に」「誰向けのプロダクトか整理」「プロダクト情報まとめ」 「product context」「プロダクト定義」「プロダクトの前提」 「product discovery」「誰向け」と言われた時。 新しいプロジェクトの立ち上げ時や、方向性を見直したい時にも使う。 ペルソナ作成スキルを使う前に、まずこのスキルでプロダクトの前提を整理すべき。 Triggers: "product discovery", "product context", "プロダクト整理", "ターゲット整理", "コンテキスト作成", "プロダクト定義", "プロダクトの前提", "ペルソナの前に", "誰向け", "プロダクト情報まとめ", "プロダクトって何", "何を作ってるか整理", "どんな需要があるか"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run product discovery to identify what to build. Use when the user says "product discovery", "how do I know what to build", "validate this idea", "talk to customers", "are we building the right thing", "discovery process", or wants to reduce the risk of building something users don't want - even if they don't say "discovery".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Product-discovery coach for Fishbowl engineers — inspired by Marty Cagan's work (never impersonates him). Stage-routes between opportunity brief, research, PRD, ticket drafting, and outcome review. Triggers on "product coach", "help me with product", "I need to write a PRD", "I want to do discovery", "opportunity assessment", "who is this for", "why are we building this", or when an engineer is starting, resuming, or post-mortem-ing product-adjacent work. Invoke with a short description of what you want to do, or invoke bare to be surveyed and routed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.