pm-lean-canvas

pm-lean-canvas is a skill for Claude Code from ljucask/pureinn-product-development. It costs 47 tokens per session (2,951 once invoked), scanned A, original, MIT.

A skill that creates a Lean Canvas, a one-page model of a product's problem, solution, customers, and business assumptions.

In plain words
What is it for?
Use it after a go/no-go decision to draft a business model, identify early adopters and risks, and mark incomplete inputs for review.
Why use it?
It helps validation-stage products make their key bets explicit without inventing missing market information.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; mentions subagents; names the AskUserQuestion tool.

Part of the pureinn-product-development plugin — 51 skills, 1 command shipped together

Good fit Use it after a go/no-go decision to draft a business model, identify early adopters and risks, and mark incomplete inputs for review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ljucask/pureinn-product-development/pm-lean-canvas
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ljucask/pureinn-product-development --skill pm-lean-canvas
Clone the repo
git clone --depth 1 https://github.com/ljucask/pureinn-product-development

Made for: Claude Code.

Or install pureinn-product-development, the plugin that ships this one along with the rest of its 51 skills, 1 command.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pm-lean-canvas

README.md
[![agentmods](https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-lean-canvas/github.svg)](https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-lean-canvas)
Your own site
<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-lean-canvas"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-lean-canvas/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for pm-lean-canvas

Your own site · 80×15
<a href="https://agentmods.dev/skills/ljucask/pureinn-product-development/pm-lean-canvas"><img src="https://agentmods.dev/badge/skills/ljucask/pureinn-product-development/pm-lean-canvas.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,951 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.02951
Opus 5 $0.00023 $0.01476
Sonnet 5 $0.00009 $0.00590
Haiku 4.5 $0.00005 $0.00295

Measured 12d ago against content hash 42e65dcbbf41, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

pm-lean-canvas scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pm-lean-canvas/SKILL.md · 313 lines

How it starts

The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PM - Lean Canvas

Agent mode (--agent)

Supports --agent: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note.

  • No flag → interactive (default); if inputs are heavy, offer agent mode.
  • --agent → obey. First check inputs are complete. Anything missing: do NOT invent it - mark [ASSUMED - what/why] in the output and summary. Never hallucinate to fill a gap.
  • Review required: the artifact contains commitments - after drafting, require the user's review before finalizing; do not close decisions autonomously.

What this skill does

Produces a one-page business model focused on problem-solution fit and early traction. Lean Canvas is optimized for the validation stage - it forces explicit problem/solution pairing, early adopter definition, and unfair advantage thinking before scaling.

Unlike the Business Model Canvas (which maps an established business), Lean Canvas maps a hypothesis. Each block is a bet that needs validation.

No invented market data or assumptions. Claude structures the canvas; user provides the business knowledge from Phase 2 research and Phase 3a Go/No-Go outcomes.


Dependencies

Recommended before running:

  • pm-hypotheses (Results mode) - Go/No-Go verdict must be GO before running this skill
  • design-thinking - Problem, UVP, and Solution blocks draw directly from design thinking synthesis
  • pm-personas - Customer Segments and Early Adopters block requires validated persona work
  • pm-market-analysis - Channels and Revenue Streams informed by market research

Produces artifacts used by:

  • pm-prd - Lean Canvas is a PRD section (business model overview)
  • pm-business-case - Revenue Streams and Cost Structure from canvas feed financial projections
  • pm-product-roadmap - channels and key metrics inform roadmap priorities

Step 0: Current state check

Check for existing artifact:

  • pureinn-workspace/[slug]/artifacts/phase-3-define/lean-canvas.md

Read the full file on GitHub · 313 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 313 lines · 47 tokens per session scan A 42e65dcbbf41

Subscribe to this mod's changes

pm-lean-canvas is a skill published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 2,951 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

ai-native-design

A workflow for turning a product brief and API contract into frontend design prompts and implementation guidance. It supports three outside design channels and keeps generated frontend work aligned with the same brief and contract.

dhslegen/digital-delivery-team · 105 tokens

backend-development

A set of instructions for building server-side code such as APIs and database-backed applications. It uses API contracts, data models, the chosen technology stack, and tests as the project’s reference points.

dhslegen/digital-delivery-team · 72 tokens

decision-gate

A decision checkpoint for software-project workflows. After each phase produces its files, it asks the user to accept the result, request a change, add information, or regenerate it before the next phase begins.

dhslegen/digital-delivery-team · 62 tokens

frontend-development

A set of instructions for building the user-facing part of a web application, such as its pages, controls, and interactions. It applies to single-page applications and follows the project’s API, product, technology, and design documents.

dhslegen/digital-delivery-team · 75 tokens

relay

A Chinese-language procedure for handing an unfinished task from one AI session to another without losing its context.

dhslegen/digital-delivery-team · 111 tokens

validation-loop

A development routine that checks each important file immediately after it is changed by running the project’s build, lint, type-check, or test commands.

dhslegen/digital-delivery-team · 53 tokens