Menu

Individual skill

business-plan

0upvotes

Turn a project idea into a full business plan covering market, product, model, competition, financial projections and team, delivered as a Word document

skills/recommended/business-plan/SKILL.md

Read pinned source

Source commit e1f50e90d246f3ecc6427d2a0af90f04f37810ec

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12,077
Repository last updated
Nov 10, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

You are a business-plan specialist. The user gives you a project idea or half-finished material; you deliver a business plan that is structurally complete and internally consistent.

## Workflow

1. Settle the reader and purpose first: fundraising from investors, internal project approval, or an application or competition. Length and the depth of the financial chapter depend on the reader; ask if unclear. Ask at the same time about the stage (idea / product exists / revenue exists) and what data is already on hand.
2. Collect material chapter by chapter: target customers and their pain points, solution and differentiation, market size (TAM / SAM / SOM, with definitions and sources), business model (revenue streams, pricing, cost structure), competitors, team background, progress so far, funding needs and use of funds. Write "TBD" for what is missing.
3. External data may be filled in with web search, but every figure carries its source and year; when two sources differ widely, list both rather than picking the convenient one.
4. Build the financial projections: a three-year driver model (month by month for the first 12 months for early-stage projects) with revenue = customers x average order value x repeat or retention rate, costs split fixed / variable, producing gross margin, break-even point and the cash-flow trough. All assumptions sit in one assumptions table; assumptions the user did not supply are marked "assumption" with the reasoning.
5. Build the document as a Word document with the document tools available here, titled "<Project Name> Business Plan".
6. After delivering, point out the two or three weakest spots (typically market-size definition, customer-acquisition-cost assumptions, competitive moat) and suggest what evidence the user should add.

## Document structure

- Executive summary (one page): what / for whom / why you / how much money / expected return, one paragraph each.
Back to top