Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Business Plan Writer

ASecurity

Write complete business plans — executive summary, market analysis, financials, and investor-ready narratives.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsrustgo

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill business-plan-writer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Business Plan Writer?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Business Plan Writer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-business-plan-writer/badge)](https://www.skillsdirectory.com/skills/aicodedecode-business-plan-writer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: business-plan-writer
description: Write complete business plans — executive summary, market analysis, financials, and investor-ready narratives.
category: business-marketing
---

## Overview

A 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/service, marketing and sales strategy, financial projections, and appendix — for audiences like investors, lenders, or internal stakeholders.

Plans should be lean where possible: a 15-page focused plan beats a 60-page bloated one.

## When to use

- Raising investment (seed, Series A, small business loans)
- Applying for grants or business competitions
- Aligning co-founders on strategy
- Planning a major expansion or new venture
- Creating an internal strategy document

- Writing a one-page lean canvas before the full plan
- Creating franchise or licensing proposals
- Documenting strategy for a board of directors
- Applying for bank loans or SBA financing
- Recruiting co-founders with a concrete vision
- Entering business plan competitions
## Core concepts

**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.

**Market sizing (TAM/SAM/SOM).** 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").

**Business model clarity.** How money is made: pricing, unit economics, sales motion, key partnerships. Include CAC, LTV, gross margin, and payback period if known.

**Competitive positioning.** Direct and indirect competitors, their strengths/weaknesses, and your differentiation. A "we have no competitors" claim destroys credibility — the alternative is always "do nothing" or a workaround.

**Financial projections.** 3–5 year P&L, cash flow, and balance sheet highlights. Show assumptions explicitly. Investors discount the numbers but scrutinize the logic.

**Risk and mitigation.** Naming risks (market, execution, regulatory, financial) with mitigation plans builds more confidence than pretending they don't exist.


**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.

**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.

**Market sizing (TAM/SAM/SOM).** TAM: everyone with the problem. SAM: those you can reach with your channels. SOM: what you can capture in 3–5 years.
Bottom-up sizing (customers × price) beats top-down ("1% of a $50B market") — investors discount top-down math heavily.
Show your arithmetic; hidden assumptions destroy credibility.
**Risk section.** Name the top 5 risks honestly (market, execution, financial, competitive, regulatory) with mitigations.
Founders fear this section; investors respect it. A plan with no risks signals naivety, not confidence.
## Practical workflow

1. **Clarify audience and purpose.** An investor plan emphasizes returns and defensibility; a bank plan emphasizes repayment ability; an internal plan emphasizes execution. Tailor accordingly.
2. **Research the market.** Size TAM/SAM/SOM bottom-up. Profile 5–8 competitors. Document trends, regulations, and customer evidence (interviews, surveys, LOIs).
3. **Draft the narrative sections.** Company, product, market analysis, marketing/sales strategy, operations, team. Keep each tight — one clear point per paragraph.
4. **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/base/worst scenarios for key assumptions.
5. **Write the executive summary last.** Distill the strongest points. End with a clear ask (amount, use of funds, terms sought).
6. **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.

**Standard structure:** Executive Summary → Company Description → Market Analysis → Organization & Management → Product/Service → Marketing & Sales → Financial Projections → Funding Request → Appendix.


**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.

**Writing order:** financial model first (it exposes whether the story works) → market analysis → operations plan → then the narrative sections → executive summary last.
Writing the summary first produces fiction; writing it last produces a summary.
**Length guide:** 20–30 pages for investors, 10–15 for internal use, 1 page (lean canvas) for early validation.
Match length to audience — nobody asked for a longer plan than they will read.
## Common pitfalls

- **Hockey-stick projections without basis.** Explosive growth curves need a credible engine (proven CAC, viral loop, contracted revenue). Otherwise they're fiction.
- **Top-down market sizing.** "1% of $X trillion" is meaningless. Build from customers you can actually reach.
- **Ignoring competition.** Claiming no competitors signals you haven't looked. Name them and explain your edge.
- **Burying the ask.** Investors shouldn't hunt for how much you want and what it's for. State it clearly.
- **Inconsistent numbers.** Revenue in the summary must match the financials. Cross-check everything.
- **Too long.** If it takes an hour to read, it won't be read. Aim for clarity and brevity; put detail in the appendix.
- **No milestones.** Plans without dated milestones and KPIs are wishes. Tie funding to achievable checkpoints.
- **Appendix as dumping ground.** Hiding weak analysis in the appendix instead of fixing it. The appendix supports; it does not excuse.
- **No sensitivity discussion.** Presenting single-point forecasts as certainties. Show which 2–3 assumptions the plan hinges on.
- **Hockey-stick without drivers.** Revenue exploding in year 3 with no explanation of what causes the inflection. Every inflection needs a named driver.
- **Ignoring competition.** "We have no competitors" — the fastest way to lose credibility. Everyone has competitors, including the status quo.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →