phuryn/lean-canvas
pm-product-strategy/skills/lean-canvas/SKILL.md
Generate a Lean Canvas with problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue. Use when exploring a lean startup canvas, testing a business hypothesis, or modeling a new venture.
$ install --global
skillsauthnpx skillsauth add phuryn/pm-skills lean-canvasInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 2:53 PM31.1s1 file scanned
SKILL.md
- name:
- lean-canvas
- description:
- Generate a Lean Canvas with problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue. Use when exploring a lean startup canvas, testing a business hypothesis, or modeling a new venture.
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
- Define the core problem(s) being solved
- Outline 2-3 solution approaches
- Craft a compelling UVP
- Identify what creates competitive advantage
- Target 1-2 customer segments
- Map acquisition channels
- Define revenue model and pricing
- Estimate cost structure
- Identify 3-5 critical metrics to track
- Surface key assumptions and hypotheses
- 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
- Startup Canvas: Product Strategy and a Business Model for a New Product
Related Skills
phuryn/strategy-red-team
testing
VerifiedTrustedCommunity
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/shipping-artifacts
tools
VerifiedTrustedCommunity
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/intended-vs-implemented
development
VerifiedTrustedCommunity
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/review-resume
testing
VerifiedTrustedCommunity
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.
7,806SKILL.mdUpdated Mar 20, 2026