phuryn/pm-skills

identify-assumptions-new

Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/phuryn/pm-skills --skill identify-assumptions-new

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Identify Assumptions (New Product)

Comprehensive risk identification across 8 categories — extending the 4 core product risks (Teresa Torres, Continuous Discovery Habits) with Ethics, Go-to-Market, Strategy & Objectives, and Team risks that are critical for new products.

Context

You are evaluating assumptions for a new product: $ARGUMENTS.

If the user provides files (business plans, research), read them first.

Domain Context

The 4 core product risks (Teresa Torres, Continuous Discovery Habits): Value, Usability, Viability, Feasibility.

For new products, extend to 8 risk categories. Good teams assume at least three-quarters of their ideas won't perform as they hope.

Instructions

The user will describe the product concept, target segment, and feature idea. Work through these steps:

  1. Think from three perspectives about why this product might fail:
  • Product Manager: Market demand, willingness to pay, competitive landscape
  • Designer: First-time user experience, onboarding, engagement
  • Engineer: Build vs. buy decisions, scalability, technical debt
  1. Identify assumptions across 8 risk categories:
  • Value: Will it create value for customers? Will they keep using it?
  • Usability: Will people figure out how to use it? Can we onboard them fast enough? Will it increase cognitive load?
  • Viability: Can we sell/monetize/finance it? Is it worth the cost? Can we support customers and help them succeed? Can we scale? Will it be compliant?
  • Feasibility: Can we do it with the current technology? Is this integration possible? Can it be efficient? Can we scale it?
  • Ethics: Should we do it at all? Are there any ethical considerations? Will it pose a risk for our customers?
  • Go-to-Market (especially critical for new products): Can we market it? Do we have the required channels? Can we convince customers to try it? Is this the right messaging for this channel? Is this the right time? Is this the right way to launch it?
  • Strategy & Objectives: What are our assumptions? Can others copy our strategy? Have we considered political, economic, legal, technological, and environmental factors? Are those the best problems to solve?
  • Team: How well will the team work together? Do we have the right people? Do we have the right tools? Will the entire team stay with us long enough?
  1. For each assumption, rate confidence and suggest a test.

Think step by step. Save as markdown.


Further Reading

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
phuryn
커뮤니티

pricing-strategy

Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity. Use when setting prices, evaluating pricing models, preparing for a pricing change, or comparing freemium vs paid approaches.

설치 수
1
GitHub Stars
2.7만
업데이트
10월 16일
phuryn
커뮤니티

product-name

Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.

설치 수
1
GitHub Stars
2.7만
업데이트
10월 16일
phuryn
커뮤니티

review-resume

Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.

설치 수
2
GitHub Stars
2.7만
업데이트
10월 16일
phuryn
커뮤니티

create-prd

Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

설치 수
1
GitHub Stars
2.7만
업데이트
10월 16일