고객발견 인터뷰 준비은(는) 무엇을 하나요?
적절한 목표, 세그먼트, 제약 조건 및 방법으로 고객 발견 인터뷰를 계획합니다. 문제 검증, 이탈 연구 또는 신제품 아이디어를 위한 인터뷰 준비 시 사용하세요.
적절한 목표, 세그먼트, 제약 조건 및 방법으로 고객 발견 인터뷰를 계획합니다. 문제 검증, 이탈 연구 또는 신제품 아이디어를 위한 인터뷰 준비 시 사용하세요.
이 스킬은 팀이 고객 발견 인터뷰를 체계적으로 계획하고 실행할 수 있도록 지원하는 전문 도구입니다. 문제 검증, 고객 이탈 연구, 신제품 아이디어 탐색 등 다양한 상황에서 인터뷰 목표를 명확히 정의하고, 적합한 고객 세그먼트를 선정하며, 시간과 자원 제약을 고려해 최적의 인터뷰 방법(예: 반구조화 인터뷰, 맥락적 질문 등)을 선택하도록 안내합니다. 주로 제품 관리자, UX 연구자, 스타트업 창업자 등 고객 중심 의사 결정이 필요한 모든 사용자에게 유용하며, Claude Code, Cursor, Codex 등 주요 AI 에이전트 플랫폼에서 활용할 수 있습니다. SKILL.md 문서는 단계별 가이드와 체크리스트를 제공하여 사용자가 인터뷰 설계 과정을 놓치지 않고 완료할 수 있도록 돕습니다. 이 스킬의 핵심은 구조화된 템플릿과 프롬프트를 통해 인터뷰 준비의 품질을 높이고, 실행 가능한 인사이트를 도출하는 데 있습니다.
npx skills add https://github.com/deanpeters/product-manager-skills/tree/main/skills/discovery-interview-prepInstalled? Explore more 연구 & 데이터 분석 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
적절한 목표, 세그먼트, 제약 조건 및 방법으로 고객 발견 인터뷰를 계획합니다. 문제 검증, 이탈 연구 또는 신제품 아이디어를 위한 인터뷰 준비 시 사용하세요.
This repo contains 20 individual skills — each has its own dedicated page.
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
Diagnose context stuffing vs. context engineering. Use when an AI workflow feels bloated, brittle, or hard to steer reliably.
Create a customer journey map across stages, touchpoints, actions, emotions, and metrics. Use when diagnosing a broken experience or aligning a team on the full customer flow.
Run a customer journey mapping workshop with adaptive questions and outputs. Use when you need to map stages, actions, emotions, pain points, and opportunities for a persona and scenario.
Guide the PM-to-Director transition across preparing, interviewing, landing, and recalibrating. Use when leadership scope is changing and you need practical coaching.
Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.
Write a clear, empathetic EOL announcement with rationale, customer impact, and next steps. Use when retiring a product, feature, or plan without creating avoidable confusion.
Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.
Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.
Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.
Evaluate feature investments using revenue impact, cost structure, ROI, and strategy. Use when deciding whether a feature deserves investment.
Evaluate pricing changes using ARPU, conversion, churn risk, NRR, and payback. Use when deciding whether a pricing move should ship.
Look up SaaS finance metrics, formulas, and benchmarks fast. Use when you need a quick metric definition, formula, or benchmark during analysis.
Uncover customer jobs, pains, and gains in a structured JTBD format. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.
Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next.
Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.