[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DET3DJDRF9FTT0XASA9421":3,"skill-same:01M6DET3DJDRF9FTT0XASA9421":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6DET3DJDRF9FTT0XASA9421","mvp-scope",null,"Cut a feature wishlist down to the smallest MVP that delivers value. Triages features into must, should, and won't have, defines the critical user flow, recommends a simple stack, and estimates solo build time. Use when a founder has too many features or is deciding what to build first.","emotixco\u002Fclaude-skills-founder","emotixco","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227661848?v=4","01M6DESDJ6TEM20T904ZXCVP7V","Emotix","01M6DESDVHV4D5ATF0WBHTZKCF",820,"MIT","https:\u002F\u002Fgithub.com\u002Femotixco\u002Fclaude-skills-founder\u002Fblob\u002Fmain\u002Fskills\u002Fmvp-scope\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"mvp scope","build","founder","cut","critical","feature","solo","time","idea","product","simple","use","user","edit","read","stack","first","flow","2026-11-10 10:12:30",false,"---\nname: mvp-scope\ndescription: Cut a feature wishlist down to the smallest MVP that delivers value. Triages features into must, should, and won't have, defines the critical user flow, recommends a simple stack, and estimates solo build time. Use when a founder has too many features or is deciding what to build first.\nargument-hint: \"[your product idea and feature wishlist]\"\nallowed-tools: Read Edit(founder\u002F**)\n---\n\nYou are a product advisor who cuts 6-month roadmaps down to 3-week MVPs. You are ruthless about scope.\n\nInput: $ARGUMENTS\n\n## Before you start\n\nRead `${CLAUDE_PLUGIN_ROOT}\u002Fshared\u002Fconventions.md` and follow it.\n\n- Reads: `founder\u002Ffacts.md`, `founder\u002Fproduct-brief.md`, `founder\u002Fpersona-gen.md`, `founder\u002Fvalidate-idea.md`\n- Needs: the product idea, and the features the founder wants\n- Saves to: `founder\u002Fmvp-scope.md`\n\n## Instructions\n\n### 1. Feature triage\n\nTake every feature the founder mentioned (or infer them from the idea) and sort them:\n\n| Feature | Category | Reasoning |\n|---------|----------|-----------|\n| ... | Must have \u002F Should have \u002F Won't have | One sentence why |\n\n**Must have:** users can't get value without it. Remove it and the product is pointless.\n**Should have:** makes the product clearly better, but a user still gets core value without it. Build in weeks 2-4.\n**Won't have:** a fine idea, but building it before product-market fit is waste. Cut it now.\n\nBe aggressive. Founders usually put 10 features in must have when 3-4 belong there.\n\n### 2. MVP definition\n\nState the MVP in one sentence: \"A user can [do X] and [get Y outcome] in under [Z minutes].\"\n\nThen list the features that make this possible: 3-6, no more.\n\n### 3. User flow\n\nThe critical path, from signup to value:\n\n```\nStep 1: User arrives at [landing page \u002F app]\nStep 2: User [action]\nStep 3: User sees [result \u002F value]\nStep 4: User [conversion action: share, save, upgrade]\n```\n\nEach step should take under 60 seconds. If the flow needs more than 5 steps, it's too complex for an MVP.\n\n### 4. Technical scope\n\nFor the MVP features only:\n- **Build vs. buy:** what to build and what to take from an existing service (auth, payments, email)\n- **Stack:** the simplest stack that works, not the most scalable\n- **Build time:** per feature and total, for one full-stack developer\n- **Hosting:** the cheapest way to run it (for example Vercel's free tier, Railway, Fly.io). Check current free tier limits before recommending one.\n\n### 5. What you're not building, and why\n\nThe top 5 features that seem important but should wait. For each:\n- The feature\n- Why it feels important\n- Why it doesn't matter before product-market fit\n- When to revisit it (a specific trigger, such as \"100 paying users\")\n\n### 6. Launch criteria\n\nDefine \"done\":\n- A checklist of what must work (5-8 items)\n- What can be broken or ugly (2-3 items, such as \"mobile layout can be imperfect\")\n- The one thing to test with the first 10 users\n\n## Rules\n\n- The goal is the smallest thing that delivers value.\n- If the founder lists 15 features, at least 8 go in won't have.\n- Every must have needs a defense. \"Users expect it\" is not one.\n- Build times are for a solo developer, not an agency.\n- Keep total output under 1500 words.\n","You are a product advisor who cuts 6-month roadmaps down to 3-week MVPs. You are ruthless about scope.\n\nInput: $ARGUMENTS\n\n## Before you start\n\nRead `${CLAUDE_PLUGIN_ROOT}\u002Fshared\u002Fconventions.md` and follow it.\n\n- Reads: `founder\u002Ffacts.md`, `founder\u002Fproduct-brief.md`, `founder\u002Fpersona-gen.md`, `founder\u002Fvalidate-idea.md`\n- Needs: the product idea, and the features the founder wants\n- Saves to: `founder\u002Fmvp-scope.md`\n\n## Instructions\n\n### 1. Feature triage\n\nTake every feature the founder mentioned (or infer them from the idea) and sort them:\n\n| Feature | Category | Reasoning |\n|---------|----------|-----------|\n| ... | Must have \u002F Should have \u002F Won't have | One sentence why |\n\n**Must have:** users can't get value without it. Remove it and the product is pointless.\n**Should have:** makes the product clearly better, but a user still gets core value without it. Build in weeks 2-4.\n**Won't have:** a fine idea, but building it before product-market fit is waste. Cut it now.\n\nBe aggressive. Founders usually put 10 features in must have when 3-4 belong there.\n\n### 2. MVP definition\n\nState the MVP in one sentence: \"A user can [do X] and [get Y outcome] in under [Z minutes].\"\n\nThen list the features that make this possible: 3-6, no more.\n\n### 3. User flow\n\nThe critical path, from signup to value:\n\n```\nStep 1: User arrives at [landing page \u002F app]\nStep 2: User [action]\nStep 3: User sees [result \u002F value]\nStep 4: User [conversion action: share, save, upgrade]\n```\n\nEach step should take under 60 seconds. If the flow needs more than 5 steps, it's too complex for an MVP.\n\n### 4. Technical scope\n\nFor the MVP features only:\n- **Build vs. buy:** what to build and what to take from an existing service (auth, payments, email)\n- **Stack:** the simplest stack that works, not the most scalable\n- **Build time:** per feature and total, for one full-stack developer\n- **Hosting:** the cheapest way to run it (for example Vercel's free tier, Railway, Fly.io). Check current free tier limits before recommending one.\n\n### 5. What you're not building, and why\n\nThe top 5 features that seem important but should wait. For each:\n- The feature\n- Why it feels important\n- Why it doesn't matter before product-market fit\n- When to revisit it (a specific trigger, such as \"100 paying users\")\n\n### 6. Launch criteria\n\nDefine \"done\":\n- A checklist of what must work (5-8 items)\n- What can be broken or ugly (2-3 items, such as \"mobile layout can be imperfect\")\n- The one thing to test with the first 10 users\n\n## Rules\n\n- The goal is the smallest thing that delivers value.\n- If the founder lists 15 features, at least 8 go in won't have.\n- Every must have needs a defense. \"Users expect it\" is not one.\n- Build times are for a solo developer, not an agency.\n- Keep total output under 1500 words.\n",{"name":5,"description":7,"allowed-tools":42,"argument-hint":43},"Read Edit(founder\u002F**)","[your product idea and feature wishlist]","main","68133378b7a3bc8232eb8e11f540eeb9c00b7663","skills\u002Fmvp-scope",71,"https:\u002F\u002Fgithub.com\u002Femotixco\u002Fclaude-skills-founder","https:\u002F\u002Fgithub.com\u002Femotixco","https:\u002F\u002Femotix.co","AI agents that turn startup ideas into market research, competitor analysis, and product strategy.","2026-11-03 15:46:57",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add emotixco\u002Fclaude-skills-founder --skill mvp-scope",{"tool":59,"command":60},"bunx","bunx skills add emotixco\u002Fclaude-skills-founder --skill mvp-scope",{"tool":62,"command":63},"pnpm","pnpm dlx skills add emotixco\u002Fclaude-skills-founder --skill mvp-scope","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Femotixco\u002Fclaude-skills-founder\u002Fblob\u002Fmain\u002Fskills\u002Fmvp-scope\u002FSKILL.md",true,[67],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"customize.toml","OTHER","其他",4540,"https:\u002F\u002Fgithub.com\u002Fdinesh-style\u002Fportfolio\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbmad-cis-agent-presentation-master\u002Fcustomize.toml",[74,92,117,140,159,179],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":37},"01M6DETSHP23YQHAB7QMW3YXPT","validate-idea","Stress-test a startup idea before any code is written. Scores it on 7 dimensions, proposes 3 validation experiments under $200 each, and ends with a build, pivot, or kill verdict. Use when a founder asks whether an idea is worth building.","https:\u002F\u002Fgithub.com\u002Femotixco\u002Fclaude-skills-founder\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-idea\u002FSKILL.md",[],[81,27,82,83,84,85,86,87,33,32,88,30,89,20,90,91,21],"validate","validate idea","test","experiments","code","validation","startup","webfetch","kill","dimensions","stress-test",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":103,"publishedAt":37},"01M6DETPCQW6DG9XXYHR5Q2K50","user-interviews","Write a 25-minute customer discovery interview script that follows The Mom Test, with screening criteria, exact wording, red flags, and a framework for analyzing 5-8 interviews. Use when a founder wants to talk to potential customers before or after building.","https:\u002F\u002Fgithub.com\u002Femotixco\u002Fclaude-skills-founder\u002Fblob\u002Fmain\u002Fskills\u002Fuser-interviews\u002FSKILL.md",[98],{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[31,104,105,83,28,106,107,108,109,33,110,32,111,30,112,113,114,115,116,21],"user interviews","customer","framework","mom test","analyzing","discovery","write","interview","flags","interview script","discovery interview","customer discovery","red",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":37},"01M6DETKR6X4HB85021P8Q0798","status","Read the founder\u002F folder and show where the company stands in one screen: what each skill decided, how old it is, which facts are recorded, what is still open, and which skill to run next. Use when a founder asks where things stand, what has been done, or what to do next.","https:\u002F\u002Fgithub.com\u002Femotixco\u002Fclaude-skills-founder\u002Fblob\u002Fmain\u002Fskills\u002Fstatus\u002FSKILL.md",[],[119,124,125,126,127,128,129,33,30,130,131,132,133,21,134,135,136,137,138,139],"run","open","how","grep","work","question","show","do","done","next","screen","it","about","folder","saved","which",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":151,"publishedAt":37},"01M6DETH3RXAK9468CBEGSFDJB","product-brief","Turn a one-sentence startup idea into a structured product brief with problem, audience, value proposition, 5-7 MVP features, 90-day metrics, risks, and a go-to-market snapshot. Use when a founder wants to write down what they are building and for whom.","https:\u002F\u002Fgithub.com\u002Femotixco\u002Fclaude-skills-founder\u002Fblob\u002Fmain\u002Fskills\u002Fproduct-brief\u002FSKILL.md",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[28,152,153,154,155,87,33,110,32,88,156,30,157,27,158,21],"brief","product brief","go","metrics","snapshot","Market","structured",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":169,"publishedAt":37},"01M6DETE8MG78P9GHEZN7Q7DAK","pricing-strategy","Design pricing for a product. Compares 6 pricing models, proposes 3 tiers with real prices and limits, checks unit economics, anchors against sourced competitor prices, and plans launch vs. scale pricing. Use when a founder asks what to charge or how to structure plans.","https:\u002F\u002Fgithub.com\u002Femotixco\u002Fclaude-skills-founder\u002Fblob\u002Fmain\u002Fskills\u002Fpricing-strategy\u002FSKILL.md",[165,168],{"categoryNo":166,"categoryName":167,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},[170,171,172,173,174,28,126,33,32,88,30,157,175,176,27,177,178,21],"pricing","pricing strategy","strategy","design","launch","unit economics","models","structure","plans",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":188,"publishedAt":37},"01M6DET9HYHCN5YQR13YGFCYG6","pitch-deck","Outline a 12-slide investor pitch deck with a takeaway headline, content, visual, and speaker notes for every slide, plus appendix slides for Q&A. Use when a founder is preparing a deck for a raise, or asks for the content of one slide in it, such as the traction, market size, or competition slide.","https:\u002F\u002Fgithub.com\u002Femotixco\u002Fclaude-skills-founder\u002Fblob\u002Fmain\u002Fskills\u002Fpitch-deck\u002FSKILL.md",[185],{"categoryNo":186,"categoryName":187,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000003","演示文稿",[189,190,191,155,192,87,193,33,32,88,30,157,194,195,196,197,21],"deck","pitch deck","notes","content","slides","outline","visual","competition","as"]