- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add wondelai/skills --skill lean-startup -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add wondelai/skills --skill lean-startup -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add wondelai/skills --skill lean-startup -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add wondelai/skills --skill lean-startup -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/wondelai/skills/tree/HEAD/lean-startup來自發布者
A systematic approach to building startups and launching new products that shortens development cycles and rapidly discovers whether a business model is viable.
Entrepreneurship is a form of management. Success doesn't require a perfect plan or brilliant insight—it requires a systematic process for testing assumptions, learning from customers, and iterating rapidly. Most startups fail not because they couldn't build what they planned, but because they built the wrong thing: treat every plan as a set of hypotheses to falsify, and spend effort to eliminate waste and accelerate validated learning, not to execute a fixed roadmap.
Goal: 10/10. Score a plan, experiment, or metric set by the five Quick Diagnostic rows—1 point each when the answer is yes, 2 points when it is also backed by evidence on the Validation Ladder (Level 3+):
State the current score and the lowest-scoring diagnostic row to fix next.
The fundamental cycle: IDEAS → BUILD (product) → MEASURE (data) → LEARN (knowledge) → back to IDEAS.
Critical insight: Plan the loop backward:
Goal: Minimize total time through the loop.
See references/build-measure-learn.md when planning an experiment—reverse-planning sequence, an experiment-design template, per-product-type loop examples, and the build/vanity-metric loop traps.
Learning what customers really want through experiments on real behavior—not feature requests, surveys, or focus groups (people mispredict their own behavior). Measure what customers do, not what they say, and run experiments that could falsify your assumptions. Vanity wins (downloads, signups without engagement) are not learning.
The Validation Ladder:
Target: Level 4-5 before building at scale.
The version of a new product that allows maximum validated learning with the least effort. Not a prototype (technical feasibility), not a beta (quality), not a minimum marketable product—a learning vehicle, often embarrassingly small and low quality, and usually much smaller than you think.
MVP Types:
Design questions: What's the riskiest assumption? What's the minimum that tests it? How do we measure whether it was validated?
See references/mvp-design.md when choosing and sizing an MVP—seven types in depth, a type-selection decision matrix, lower/upper sizing bounds, and the MVP Design Canvas.
The assumptions that, if wrong, will cause your business to fail. Identify them, prioritize by risk (which failure would be fatal?), and test the riskiest first—never in order of ease.
Example—Dropbox: Leap of faith: "people will download and use a file sync tool." Test: explainer video before building scale infrastructure. Result: beta list grew from 5,000 to 75,000 overnight—demand validated.
See references/assumptions.md when mapping and ranking assumptions—the Impact-Uncertainty matrix, a prioritization scoring template, test methods per assumption type, and industry-specific assumption lists.
Measuring progress when traditional metrics fail: revenue and customers start at zero, and vanity metrics look good without driving decisions.
Measure current reality precisely, even if it's zero or embarrassing: conversion funnel (signup → active → retained → paying), engagement (DAU/MAU, session length, features used), economics (CAC, LTV, churn).
Run experiments to improve baseline metrics: A/B test pricing ($9 vs. $19/mo), onboarding completion rates, acquisition channels (SEO vs. paid vs. referral). Each experiment targets a measurable improvement through validated learning.
When tuning stalls, make the evidence-based call (criteria and pivot types below in Pivot or Persevere).
See references/innovation-accounting.md when building the baseline dashboard—funnel, cohort, and economics metric frameworks.
Vanity metrics make you feel good but don't change behavior; actionable metrics drive decisions and clarify cause and effect.
Three characteristics of actionable metrics: actionable (clear cause-and-effect, reproducible), accessible (simple, understood by everyone), auditable (underlying data can be checked).
Example: Vanity: "We have 100,000 users!" Actionable: "Channel X users retain 2x better than channel Y—double down on X."
Cohort analysis: Group users by signup date and track behavior over time—the only way to see whether the product is actually improving.
See references/metrics.md when building a cohort table or choosing what to track—a five-step cohort walkthrough and AARRR (Pirate Metrics) aligned with Lean Startup stages.
A pivot is a structured course correction designed to test a new hypothesis about the product, strategy, or engine of growth.
Pivot when: experiments repeatedly fail to validate hypotheses, metrics stay flat despite iterations, customer feedback contradicts the vision, or progress is too slow for the runway. Persevere when: metrics are improving (even slowly), clear learning is happening, and adjustments move the right direction.
Pivot Types:
Cadence: Successful startups commonly pivot 1-5 times before product-market fit. Anti-pattern: "pivoting" without validating that the new direction solves the core problem.
See references/pivots.md when the data suggests a pivot—the data-driven pivot signals, a structured pivot-meeting agenda, leading indicators, and the Instagram/Slack/YouTube pivot stories.
How a startup acquires and retains customers sustainably. Pick one engine, optimize it, then consider adding others—running multiple engines simultaneously dilutes focus and learning.
Retention-driven: growth rate = new customer acquisition rate − churn rate. Track churn rate, retention cohorts (30/60/90 days), and DAU/MAU. Fits SaaS, subscriptions, social networks. Strategy: improve the product until natural growth exceeds churn.
Customers bring customers: viral coefficient = (% who invite) × (invites sent) × (% who join); above 1.0 means exponential, self-sustaining growth. Track the coefficient, viral cycle time, and referral attribution. Fits Dropbox, Hotmail, WhatsApp. Strategy: build virality into the product itself.
Spend to acquire: requires LTV > CAC (target LTV/CAC > 3x). Track CAC, LTV, and payback period. Fits e-commerce and traditional businesses. Strategy: optimize until each customer's profit funds acquiring more.
See references/growth-engines.md when picking or tuning an engine—churn-reduction tactics, the K-factor and viral-loop design, LTV/CAC optimization, a channel-economics table, and the product-to-engine matching framework.
Root cause analysis: when a problem occurs, ask "why?" five times, then invest proportionally at every level—not just the symptom.
Example—website went down:
Proportional investments: fix the bug (1), add memory monitoring (2), implement code review (3-4), slow down to build quality processes (5). Anti-pattern: stopping at level 1.
See references/five-whys.md when facilitating a session—three worked examples (outage, churn spike, launch failure) and how to handle diverging chains, blame creep, and root causes outside your control.
Work in small batches for faster feedback loops, easier pivots, less waste when you're wrong, and faster time to market.
Continuous deployment is the ultimate small batch: deploy every commit, catch bugs immediately, learn continuously, reduce risk per release.
See references/small-batches.md when setting up faster release cadence—the continuous-deployment pipeline and prerequisites, feature-flag types, a progressive-rollout checklist, and work-decomposition techniques.
Phase 1—Problem/Solution Fit: validate that the problem exists and customers care, via customer discovery, smoke tests, and concierge MVPs. Metric: customers willing to pay or commit.
Phase 2—Product/Market Fit: build the MVP and iterate on usage data. Metric: high retention, organic growth, strong engagement.
Phase 3—Scale: optimize the growth engine and unit economics. Metric: sustainable, profitable growth. Anti-pattern: skipping Phases 1-2 and jumping straight to scale.
By context:
See references/applications.md for context-specific playbooks (SaaS, corporate innovation, features), and references/case-studies.md for the full Dropbox, IMVU, Zappos, and Groupon stories—including failures—when you want a worked precedent for the bet in front of you.
Audit any product development plan:
For the complete framework, research, and case studies:
Eric Ries is an entrepreneur and author who developed the Lean Startup methodology as co-founder and CTO of IMVU, where he pioneered the continuous deployment and customer development practices behind it. The Lean Startup has been translated into over 30 languages and shaped startup culture worldwide. He later created the Long-Term Stock Exchange (LTSE).
Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity met
---name: lean-startupdescription: Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use…---# lean-startup/SKILL.md總覽
Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", "test assumptions", "innovation accounting", "build-measure-learn", "minimum viable experiment", "should we pivot", "test a business idea cheaply", or "build the smallest version first". Also trigger when deciding what to include in a first version, measuring startup progress, or evaluating whether to change direction on a product bet. Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done.
常見問題
從發布者下載 lean-startup/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/wondelai/skills。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。