foundation-lean-canvas
Lean Canvas
A lean canvas is a one-page business thesis that makes your assumptions about problem, customer, solution, and viability explicit and testable. Developed by Ash Maurya from Alex Osterwalder's Business Model Canvas, it is specifically adapted for startups and product teams operating under uncertainty. Nine interlocking blocks force you to articulate the whole picture at once so that changing one block's assumptions surfaces the ripple effect on the others.
This skill is a strategic hub, not a specialist tool. It produces the integrated one-page artifact and cross-links to deeper PM skills (/problem-statement, /persona, /jtbd-canvas, /solution-brief, /competitive-analysis, /experiment-design) for single-block depth when needed.
Supported Modes
content(default) produces the nine-block canvas as structured markdown.visualproduces the markdown canvas AND writes a self-contained, attractive.htmlfile to disk usingreferences/html-template.htmlas the layout scaffold. The HTML renders the canonical Maurya nine-block layout with polished typography, subtle per-column color accents, confidence badges per block, and print-ready A3 landscape styling. No external assets or CDN dependencies: the file opens correctly in a browser with no network access.
If mode is omitted, default to content and state that fallback explicitly.
When to Use
More from product-on-purpose/pm-skills
deliver-acceptance-criteria
Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.
112deliver-prd
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
108define-hypothesis
Defines a testable hypothesis with clear success metrics and validation approach. Use when forming assumptions to test, designing experiments, or aligning team on what success looks like.
105discover-competitive-analysis
Creates a structured competitive analysis comparing features, positioning, and strategy across competitors. Use when entering a market, planning differentiation, or understanding the competitive landscape.
105deliver-user-stories
Generates user stories with clear acceptance criteria from product requirements or feature descriptions. Use when breaking down features for sprint planning, writing tickets, or communicating requirements to engineering.
102define-problem-statement
Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
101