[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMETFKYHRA66YA198PTRWF":3,"skill-same:01M7EMETFKYHRA66YA198PTRWF":47},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMETFKYHRA66YA198PTRWF","business-plan-writer",null,"Write complete business plans — executive summary, market analysis, financials, and investor-ready narratives.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-business-plan-writer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: business-plan-writer\ndescription: Write complete business plans — executive summary, market analysis, financials, and investor-ready narratives.\ncategory: business-marketing\n---\n\n## Overview\n\nA business plan is a structured argument that an opportunity is real, the approach is sound, and the numbers work. This skill covers writing each section — executive summary, company description, market analysis, organization, product\u002Fservice, marketing and sales strategy, financial projections, and appendix — for audiences like investors, lenders, or internal stakeholders.\n\nPlans should be lean where possible: a 15-page focused plan beats a 60-page bloated one.\n\n## When to use\n\n- Raising investment (seed, Series A, small business loans)\n- Applying for grants or business competitions\n- Aligning co-founders on strategy\n- Planning a major expansion or new venture\n- Creating an internal strategy document\n\n- Writing a one-page lean canvas before the full plan\n- Creating franchise or licensing proposals\n- Documenting strategy for a board of directors\n- Applying for bank loans or SBA financing\n- Recruiting co-founders with a concrete vision\n- Entering business plan competitions\n## Core concepts\n\n**Executive summary.** Written last, read first. One to two pages: the opportunity, the solution, the market, the business model, traction, the team, and the ask. If a reader only reads this, they should understand the whole bet.\n\n**Market sizing (TAM\u002FSAM\u002FSOM).** Total Addressable Market → Serviceable Available Market → Serviceable Obtainable Market. Bottom-up sizing (customers × price) is far more credible than top-down (\"1% of a trillion-dollar market\").\n\n**Business model clarity.** How money is made: pricing, unit economics, sales motion, key partnerships. Include CAC, LTV, gross margin, and payback period if known.\n\n**Competitive positioning.** Direct and indirect competitors, their strengths\u002Fweaknesses, and your differentiation. A \"we have no competitors\" claim destroys credibility — the alternative is always \"do nothing\" or a workaround.\n\n**Financial projections.** 3–5 year P&L, cash flow, and balance sheet highlights. Show assumptions explicitly. Investors discount the numbers but scrutinize the logic.\n\n**Risk and mitigation.** Naming risks (market, execution, regulatory, financial) with mitigation plans builds more confidence than pretending they don't exist.\n\n\n**Lean plan alternative.** For early-stage ventures, a one-page lean canvas (problem, solution, key metrics, unfair advantage, channels, cost structure, revenue streams) often beats a 40-page plan. Write the full plan when external stakeholders (investors, lenders) require it; use the lean version for internal alignment.\n\n**Use of funds.** Investors scrutinize this section closely: tie every dollar to milestones ($500k → 12 months runway → $1M ARR and 50 enterprise customers). Vague allocations (marketing: $200k) signal unfocused thinking.\n\n**Market sizing (TAM\u002FSAM\u002FSOM).** TAM: everyone with the problem. SAM: those you can reach with your channels. SOM: what you can capture in 3–5 years.\nBottom-up sizing (customers × price) beats top-down (\"1% of a $50B market\") — investors discount top-down math heavily.\nShow your arithmetic; hidden assumptions destroy credibility.\n**Risk section.** Name the top 5 risks honestly (market, execution, financial, competitive, regulatory) with mitigations.\nFounders fear this section; investors respect it. A plan with no risks signals naivety, not confidence.\n## Practical workflow\n\n1. **Clarify audience and purpose.** An investor plan emphasizes returns and defensibility; a bank plan emphasizes repayment ability; an internal plan emphasizes execution. Tailor accordingly.\n2. **Research the market.** Size TAM\u002FSAM\u002FSOM bottom-up. Profile 5–8 competitors. Document trends, regulations, and customer evidence (interviews, surveys, LOIs).\n3. **Draft the narrative sections.** Company, product, market analysis, marketing\u002Fsales strategy, operations, team. Keep each tight — one clear point per paragraph.\n4. **Build the financials.** Start from unit economics, then scale: revenue model → cost structure → monthly cash flow for year 1, annual for years 2–5. Include best\u002Fbase\u002Fworst scenarios for key assumptions.\n5. **Write the executive summary last.** Distill the strongest points. End with a clear ask (amount, use of funds, terms sought).\n6. **Review and pressure-test.** Have someone skeptical read it. Fix every \"so what?\" and \"says who?\". Check that numbers tie across sections — inconsistent figures kill trust instantly.\n\n**Standard structure:** Executive Summary → Company Description → Market Analysis → Organization & Management → Product\u002FService → Marketing & Sales → Financial Projections → Funding Request → Appendix.\n\n\n**Financial narrative check:** for every major number, write one sentence explaining the driver (Revenue grows 3x in year 2 driven by enterprise expansion at $50k ACV). If you cannot explain a number's driver, the model needs work.\n\n**Writing order:** financial model first (it exposes whether the story works) → market analysis → operations plan → then the narrative sections → executive summary last.\nWriting the summary first produces fiction; writing it last produces a summary.\n**Length guide:** 20–30 pages for investors, 10–15 for internal use, 1 page (lean canvas) for early validation.\nMatch length to audience — nobody asked for a longer plan than they will read.\n## Common pitfalls\n\n- **Hockey-stick projections without basis.** Explosive growth curves need a credible engine (proven CAC, viral loop, contracted revenue). Otherwise they're fiction.\n- **Top-down market sizing.** \"1% of $X trillion\" is meaningless. Build from customers you can actually reach.\n- **Ignoring competition.** Claiming no competitors signals you haven't looked. Name them and explain your edge.\n- **Burying the ask.** Investors shouldn't hunt for how much you want and what it's for. State it clearly.\n- **Inconsistent numbers.** Revenue in the summary must match the financials. Cross-check everything.\n- **Too long.** If it takes an hour to read, it won't be read. Aim for clarity and brevity; put detail in the appendix.\n- **No milestones.** Plans without dated milestones and KPIs are wishes. Tie funding to achievable checkpoints.\n- **Appendix as dumping ground.** Hiding weak analysis in the appendix instead of fixing it. The appendix supports; it does not excuse.\n- **No sensitivity discussion.** Presenting single-point forecasts as certainties. Show which 2–3 assumptions the plan hinges on.\n- **Hockey-stick without drivers.** Revenue exploding in year 3 with no explanation of what causes the inflection. Every inflection needs a named driver.\n- **Ignoring competition.** \"We have no competitors\" — the fastest way to lose credibility. Everyone has competitors, including the status quo.\n","## Overview\n\nA business plan is a structured argument that an opportunity is real, the approach is sound, and the numbers work. This skill covers writing each section — executive summary, company description, market analysis, organization, product\u002Fservice, marketing and sales strategy, financial projections, and appendix — for audiences like investors, lenders, or internal stakeholders.\n\nPlans should be lean where possible: a 15-page focused plan beats a 60-page bloated one.\n\n## When to use\n\n- Raising investment (seed, Series A, small business loans)\n- Applying for grants or business competitions\n- Aligning co-founders on strategy\n- Planning a major expansion or new venture\n- Creating an internal strategy document\n\n- Writing a one-page lean canvas before the full plan\n- Creating franchise or licensing proposals\n- Documenting strategy for a board of directors\n- Applying for bank loans or SBA financing\n- Recruiting co-founders with a concrete vision\n- Entering business plan competitions\n## Core concepts\n\n**Executive summary.** Written last, read first. One to two pages: the opportunity, the solution, the market, the business model, traction, the team, and the ask. If a reader only reads this, they should understand the whole bet.\n\n**Market sizing (TAM\u002FSAM\u002FSOM).** Total Addressable Market → Serviceable Available Market → Serviceable Obtainable Market. Bottom-up sizing (customers × price) is far more credible than top-down (\"1% of a trillion-dollar market\").\n\n**Business model clarity.** How money is made: pricing, unit economics, sales motion, key partnerships. Include CAC, LTV, gross margin, and payback period if known.\n\n**Competitive positioning.** Direct and indirect competitors, their strengths\u002Fweaknesses, and your differentiation. A \"we have no competitors\" claim destroys credibility — the alternative is always \"do nothing\" or a workaround.\n\n**Financial projections.** 3–5 year P&L, cash flow, and balance sheet highlights. Show assumptions explicitly. Investors discount the numbers but scrutinize the logic.\n\n**Risk and mitigation.** Naming risks (market, execution, regulatory, financial) with mitigation plans builds more confidence than pretending they don't exist.\n\n\n**Lean plan alternative.** For early-stage ventures, a one-page lean canvas (problem, solution, key metrics, unfair advantage, channels, cost structure, revenue streams) often beats a 40-page plan. Write the full plan when external stakeholders (investors, lenders) require it; use the lean version for internal alignment.\n\n**Use of funds.** Investors scrutinize this section closely: tie every dollar to milestones ($500k → 12 months runway → $1M ARR and 50 enterprise customers). Vague allocations (marketing: $200k) signal unfocused thinking.\n\n**Market sizing (TAM\u002FSAM\u002FSOM).** TAM: everyone with the problem. SAM: those you can reach with your channels. SOM: what you can capture in 3–5 years.\nBottom-up sizing (customers × price) beats top-down (\"1% of a $50B market\") — investors discount top-down math heavily.\nShow your arithmetic; hidden assumptions destroy credibility.\n**Risk section.** Name the top 5 risks honestly (market, execution, financial, competitive, regulatory) with mitigations.\nFounders fear this section; investors respect it. A plan with no risks signals naivety, not confidence.\n## Practical workflow\n\n1. **Clarify audience and purpose.** An investor plan emphasizes returns and defensibility; a bank plan emphasizes repayment ability; an internal plan emphasizes execution. Tailor accordingly.\n2. **Research the market.** Size TAM\u002FSAM\u002FSOM bottom-up. Profile 5–8 competitors. Document trends, regulations, and customer evidence (interviews, surveys, LOIs).\n3. **Draft the narrative sections.** Company, product, market analysis, marketing\u002Fsales strategy, operations, team. Keep each tight — one clear point per paragraph.\n4. **Build the financials.** Start from unit economics, then scale: revenue model → cost structure → monthly cash flow for year 1, annual for years 2–5. Include best\u002Fbase\u002Fworst scenarios for key assumptions.\n5. **Write the executive summary last.** Distill the strongest points. End with a clear ask (amount, use of funds, terms sought).\n6. **Review and pressure-test.** Have someone skeptical read it. Fix every \"so what?\" and \"says who?\". Check that numbers tie across sections — inconsistent figures kill trust instantly.\n\n**Standard structure:** Executive Summary → Company Description → Market Analysis → Organization & Management → Product\u002FService → Marketing & Sales → Financial Projections → Funding Request → Appendix.\n\n\n**Financial narrative check:** for every major number, write one sentence explaining the driver (Revenue grows 3x in year 2 driven by enterprise expansion at $50k ACV). If you cannot explain a number's driver, the model needs work.\n\n**Writing order:** financial model first (it exposes whether the story works) → market analysis → operations plan → then the narrative sections → executive summary last.\nWriting the summary first produces fiction; writing it last produces a summary.\n**Length guide:** 20–30 pages for investors, 10–15 for internal use, 1 page (lean canvas) for early validation.\nMatch length to audience — nobody asked for a longer plan than they will read.\n## Common pitfalls\n\n- **Hockey-stick projections without basis.** Explosive growth curves need a credible engine (proven CAC, viral loop, contracted revenue). Otherwise they're fiction.\n- **Top-down market sizing.** \"1% of $X trillion\" is meaningless. Build from customers you can actually reach.\n- **Ignoring competition.** Claiming no competitors signals you haven't looked. Name them and explain your edge.\n- **Burying the ask.** Investors shouldn't hunt for how much you want and what it's for. State it clearly.\n- **Inconsistent numbers.** Revenue in the summary must match the financials. Cross-check everything.\n- **Too long.** If it takes an hour to read, it won't be read. Aim for clarity and brevity; put detail in the appendix.\n- **No milestones.** Plans without dated milestones and KPIs are wishes. Tie funding to achievable checkpoints.\n- **Appendix as dumping ground.** Hiding weak analysis in the appendix instead of fixing it. The appendix supports; it does not excuse.\n- **No sensitivity discussion.** Presenting single-point forecasts as certainties. Show which 2–3 assumptions the plan hinges on.\n- **Hockey-stick without drivers.** Revenue exploding in year 3 with no explanation of what causes the inflection. Every inflection needs a named driver.\n- **Ignoring competition.** \"We have no competitors\" — the fastest way to lose credibility. Everyone has competitors, including the status quo.\n",{"name":5,"category":24,"description":7},"business-marketing","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-business-plan-writer",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill business-plan-writer",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill business-plan-writer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill business-plan-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-business-plan-writer\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]