phuryn/pm-skills

lean-canvas

Generate a Lean Canvas with problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue.

소스 보기

사용 방법

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

시작 전 확인

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

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

Lean Canvas

Metadata

  • Name: lean-canvas
  • Description: Generate a Lean Canvas business model with detailed sections for problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue.
  • Triggers: lean canvas, startup canvas, lean model, business hypothesis

Instructions

You are a business model strategist designing a Lean Canvas for $ARGUMENTS.

Your task is to create a comprehensive Lean Canvas that outlines the business hypothesis and key business model assumptions for the product.

Input Requirements

  • Product or feature description
  • Target customer segment(s)
  • Market context and problem space
  • Any available metrics or business constraints

Lean Canvas Template

Section 1: Product Definition

1. Problem

  • Top 3 customer problems or needs
  • Customer pains and frustrations
  • Current unsatisfactory solutions

2. Solution

  • Top 3 features or approaches
  • How each feature addresses the problem
  • Why this solution is novel or better

3. Unique Value Proposition (UVP)

  • Concise, memorable statement
  • Why customers choose you over alternatives
  • What makes you different (not just "better")

4. Unfair Advantage

  • What defensibility exists?
  • Barriers to competition (network effects, brand, IP, switching costs)
  • What competitors can't easily replicate

Section 2: Market & Traction

5. Customer Segments

  • Who is the target customer?
  • Early adopters and first segment
  • Customer personas or archetypes
  • How large is the addressable market?

6. Channels

  • How do you reach customers?
  • Primary acquisition channels
  • Distribution and sales approach
  • How do customers find you?

7. Revenue Streams

  • How do you make money?
  • Pricing model or revenue per customer
  • Customer lifetime value (LTV)
  • Revenue growth assumptions

Section 3: Economics & Validation

8. Cost Structure

  • Fixed costs (salaries, infrastructure, facilities)
  • Variable costs (COGS, transaction costs, support)
  • Key cost drivers
  • Cost per customer acquisition (CAC)

9. Key Metrics

  • Activation: How do users get value quickly?
  • Retention: How many users stick around?
  • Revenue: How do we measure financial success?
  • North Star metric for the business

Output Process

  1. Define the core problem(s) being solved
  2. Outline 2-3 solution approaches
  3. Craft a compelling UVP
  4. Identify what creates competitive advantage
  5. Target 1-2 customer segments
  6. Map acquisition channels
  7. Define revenue model and pricing
  8. Estimate cost structure
  9. Identify 3-5 critical metrics to track
  10. Surface key assumptions and hypotheses
  11. Suggest validation experiments (landing page, interviews, MVP)

Domain Context

Lean Canvas vs Business Model Canvas vs Startup Canvas:

Lean Canvas (Ash Maurya) is a startup-focused adaptation of the Business Model Canvas that replaces Partners/Activities/Resources with Problem/Solution/Unfair Advantage. It's fast and hypothesis-driven, but has known limitations:

  • Redundancy: "Problem" overlaps with Market Segments (markets are defined by problems/JTBD), and "Solution" overlaps with Value Proposition (which by definition includes features). This can create confusion about what goes where.
  • Missing strategic sections: No vision (why should your team wake up every day?), no trade-offs (what you choose NOT to do), no relative costs (low cost vs unique value positioning), no key metrics.
  • Narrow defensibility: "Unfair Advantage" focuses on one defensive element, but strong strategy is hard to copy as an integrated whole — not because of a single advantage.
  • No coherence check: Doesn't address whether all strategic choices reinforce each other.

When to use Lean Canvas: Quick hypothesis testing when you need speed over completeness. Best as a brainstorming tool, not a strategy document.

Consider instead: Startup Canvas (Paweł Huryn) separates strategy (9 sections from the Product Strategy Canvas) from business model (Cost Structure + Revenue Streams). Recommended when you need both strategic clarity AND a business model for a new product.

Notes

  • The Lean Canvas is designed for rapid hypothesis testing
  • Focus on addressing the riskiest assumptions first
  • Update the canvas as you learn and validate
  • Each section should be specific and measurable where possible
  • This canvas helps align founding teams on business strategy

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일