proto-persona은(는) 무엇을 하나요?
현재 연구, 시장 신호 및 팀 지식을 바탕으로 프로토-페르소나를 생성합니다. 더 깊은 검증 전에 작업 가능한 고객 프로필이 필요할 때 사용하세요.
현재 연구, 시장 신호 및 팀 지식을 바탕으로 프로토-페르소나를 생성합니다. 더 깊은 검증 전에 작업 가능한 고객 프로필이 필요할 때 사용하세요.
이 스킬은 기존 연구 데이터, 시장 신호, 팀의 내부 지식을 종합하여 프로토-페르소나(proto-persona)를 신속하게 생성합니다. 프로토-페르소나는 완전한 사용자 조사가 어려운 상황에서도 팀이 고객 중심의 의사 결정을 내릴 수 있도록 돕는 경량화된 고객 프로필입니다. 주로 AI 에이전트(Claude Code, Cursor 등)와 통합되어 프롬프트 기반으로 작동하며, 사용자는 관련 정보를 입력하거나 맥락을 제공하면 스킬이 자동으로 구조화된 페르소나 초안을 만들어냅니다. 이를 통해 제품 개발 초기 단계에서 가설을 빠르게 수립하고, 사용자 니즈와 행동 패턴을 예측하며, 향후 심층 검증의 방향을 설정할 수 있습니다. 개발자, 제품 관리자, UX 디자이너 모두에게 유용하며, 특히 시간과 자원이 제한된 환경에서 효과적입니다.
npx skills add https://github.com/deanpeters/product-manager-skills/tree/main/skills/proto-personaInstalled? 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.
Plan customer discovery interviews with the right goal, segment, constraints, and method. Use when preparing interviews for problem validation, churn research, or new product ideas.
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.
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.