Skip to main content
skill CX Codex

seed-plan — Claude Code skill: startup plan and installation

The seed-plan Claude Code skill builds a nine-section business plan from a startup idea. It runs when asked to draft or check a plan, work out unit economics, or prepare for /seed-deck.

MIT ★ 197 updated 2026-11-01

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add Jakeschincariol/seed-skill
/plugin install seed-skill@seed-skill
Open on GitHub

What seed-plan does

The skill helps write the nine parts of a business plan, then produces seed/plan.md and seed/plan.json. It stores shared startup details in seed/config.json, calculates unit economics, and flags blank sections or figures that conflict across files.

Its calculations draw on seed/market.json, seed/competitors.json, and seed/model.json, produced by /seed-market, /seed-scout, and /seed-model. The included plan.py script has init, build, and check commands and requires python3. Without those companion files, the plan lacks the market, competitor, and financial-model figures.

Checks catch issues such as use of funds that does not match the raise or a market estimate larger than TAM. The check command exits with code 0 when checks pass and 1 when something needs fixing.

What it helps with

  • draft the nine sections of a startup business plan
  • bring market, competitor, and model figures into the plan
  • calculate CAC payback and LTV:CAC
  • spot blank sections and figures that conflict across files

Example prompts for the agent

  • Build a business plan for my startup idea from the files in this project.
  • Check my plan for figures that disagree across files.
  • Calculate unit economics and prepare the plan before /seed-deck.

How to install seed-plan

1Plugin marketplace

/plugin marketplace add Jakeschincariol/seed-skill
/plugin install seed-skill@seed-skill

This installs the whole seed-skill plugin with all its skills

2Skills CLI (Vercel)

npx skills add Jakeschincariol/seed-skill --skill seed-plan -a claude-code

3Manually: put the files in place

~/.claude/skills/seed-plan/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/seed-plan/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about seed-plan

How do I install seed-plan in Claude Code?

Add its marketplace with /plugin marketplace add Jakeschincariol/seed-skill, then install it with /plugin install seed-skill@seed-skill.

What does seed-plan do?

It helps draft a nine-part business plan, brings in market and financial figures from companion skill files, and checks for missing sections or inconsistent numbers.

What does seed-plan need to run?

The script requires python3. Its calculations use seed/market.json, seed/competitors.json, and seed/model.json, created by /seed-market, /seed-scout, and /seed-model.

Source text

SKILL.md · MIT
---
name: seed-plan
description: >-
  Business Planner. Turns your idea into a business plan investors can read:
  the nine sections (executive summary, problem, solution, market,
  competition, business model, go-to-market, financial plan, use of funds),
  written with you, with the numbers pulled from the other seed skills'
  files: TAM, SAM and SOM from seed/market.json, competitors' weak points
  from seed/competitors.json, revenue, breakeven and runway from
  seed/model.json. Computes the unit economics (take rate, contribution per
  order, CAC payback, LTV:CAC) and flags empty sections and numbers that
  disagree between files. Writes seed/config.json, seed/plan.json and
  seed/plan.md. Use when the user says "turn my idea into a business plan",
  "write my business plan", "I have a startup idea", "help me plan my
  startup", "check my plan", "unit economics", or before /seed-deck.
argument-hint: "[init --name NAME --one-liner TEXT | build | check]"
---

# seed-plan

The Business Planner turns an idea into the document behind a raise. It sets
up the startup's shared config (name, one-liner, the raise, the founder), lays
out the nine sections every investor expects, and, once Claude and the
founder have written them, stitches in the numbers the other skills found:
the market size, the competitors' weak points, the model's revenue, breakeven
and runway. It works out the unit economics itself and checks the whole thing
for holes: an empty section, a raise that is $1.5M in one file and $1.2M in
another, a use of funds that does not add up, a market share bigger than the
market. A plan is a way to think clearly, not a promise of funding: the pack
does the work, investors decide.

`${CLAUDE_SKILL_DIR}` below is this skill's folder (where this SKILL.md lives).

```bash
python3 "${CLAUDE_SKILL_DIR}/plan.py" init --name "Leashly" --one-liner "A dog-walking app with flat prices and a backup walker on every walk" \
  --raise 1.5M --instrument "post-money SAFE" --founder "Your Name" --email [email protected] \
  --tagline "Dog walks without the surprise fees."
python3 "${CLAUDE_SKILL_DIR}/plan.py" build                 # seed/plan.md + the numbers in seed/plan.json
python3 "${CLAUDE_SKILL_DIR}/plan.py" check                 # the checks only: exit 0 clean, 1 something to fix
```

Other flags: `--dir PATH` (default `./seed`), `init --brand/--ink/--accent
#RRGGBB` (the deck's colours), `init --address`, `--sector`, `--geography`,
`--stage`, `init --force` (start again), `build --today YYYY-MM-DD`, `--json`.

## What it reads and writes

| file | what |
| --- | --- |
| `config.example.json` (this folder) | the shape of `seed/config.json`, filled in for Leashly |
| `seed/config.json` | `init` writes it: the startup (name, one-liner, sector, stage, geography, raise, instrument), the founder (name, email, company address), `sec_user_agent` and the outreach limits (daily cap 20, follow-ups after 3 and 7 business days, 3 touches). Every seed skill reads it |
| `seed/plan.json` | `init` writes the skeleton; Claude writes each section's `text`, `pitch` (one line for the slide) and `points` (up to 3), plus `tagline`, `team` and `brand`. `build` adds `numbers`, `flags`, `notes` and the build date |
| `seed/market.json` | from `/seed-market`: TAM, SAM, SOM and their sourced inputs |
| `seed/competitors.json` | from `/seed-scout`: each app's rating, ratings, low reviews and weak point |
| `seed/model.json` | from `/seed-model`: the assumptions, the 36 months and the summary |
| `seed/plan.md` | `build` writes it: the plan with a key-numbers table, the checks and the nine sections with their tables |

## The unit economics

Computed from the model's assumptions, exactly, and shown in the plan:

| number | how |
| --- | --- |
| revenue per order | price x take rate |
| contribution per order | revenue per order minus the costs of one order (card fees, per-order costs) |
| CAC payback | CAC / (contribution per order x orders per customer a month), in months |
| LTV | contribution per customer a month / monthly churn |
| LTV:CAC | LTV / CAC (most seed investors look for 3x or more) |

## The checks

- **Flags (fix before anyone reads it):** an empty section; a missing
  market.json, model.json or competitors.json; a raise that disagrees
  between config.json and model.json; a use of funds that does not add up
  to the raise; a SOM above the SAM or a SAM above the TAM; year 3 GMV above
  the SOM (the model sells more than the market you said you could win); a
  model.json that no longer matches its own assumptions; a contribution at
  or below $0.
- **Notes (worth a look):** a number in a section's text that is in none of
  the files (years and counts of 10 or less are skipped); LTV:CAC under 3x;
  CAC payback over 12 months; cash that runs out inside 36 months; no
  breakeven; no tagline, no team, an empty pitch line.

## Steps

1. Run `plan.py init` with the startup's name, one-liner, the raise and the
   founder's own name and work email. The email is the one outreach goes
   from: never use anyone else's.
2. Run `/seed-scout`, `/seed-market` and `/seed-model` if their files are
   missing. The plan's numbers come from them, not from memory.
3. Write the nine sections into `seed/plan.json` with the founder, one at a
   time. Plain words, short paragraphs. Every number you write should exist
   in one of the files; if the founder gives a new number, add it to the
   right file first (the market inputs, the assumptions).
4. Give each section a `pitch`: one line, a slide's worth (the deck's lint
   allows 35 words a slide). Give the solution and go-to-market up to 3
   `points`. Add the `team` (real people only) and a `tagline`.
5. Run `plan.py build`. Read back the key numbers and every flag and note.
6. Fix the flags (in the file the flag names), then build again until it
   says every check passed. Never change a number to silence a check
   without the founder's yes.
7. Hand off to `/seed-deck` to turn the plan into the 10-slide deck.

## Example: the reel

Leashly (fictional): "A dog-walking app with flat prices and a backup walker
on every walk", raising a $1.5M seed on a post-money SAFE to launch in 3
cities. `plan.py build` reads the reel's competitor numbers (Rover 4.9 stars
and 515,771 ratings, 106 of 341 recent 1 and 2 star reviews mention fees;
Wag! 4.8 stars and 67,447 ratings, 81 of 324 mention cancellations), the
market (71M US homes with a dog, $158B US pet spend in 2025, a top-down
TAM of $8.5B, SAM $228M, SOM $22.8M) and the model:

```
Leashly: business plan, 9 of 9 sections written.
  Per walk     price $25.00, take 15% = $3.75, contribution $2.23
  LTV:CAC      4.24x, CAC payback 3.37 months
Every check passed: no empty sections, and the numbers agree between files.
Wrote seed/plan.md and seed/plan.json.
Next: /seed-deck turns plan.json into the 10-slide deck.
```

The plan's key numbers: revenue $467,400 / $1,586,640 / $2,993,520 in years
1 to 3, breakeven in month 29 (May 2029), peak burn $82,801 a month, and the
cash lasts all 36 months (low point $252,553). Year 3 GMV ($19.96M) sits
under the $22.8M SOM, so that check passes.

## Rules

- Never promise funding, in the plan or in the chat. Raising money depends
  on the business; investors decide.
- Projections come from the founder's own assumptions. Say so wherever the
  plan shows revenue or runway. Not investment advice.
- No invented numbers: every figure traces to a file, and every market input
  carries its source.
- The team slide and section list real people with their real roles.

© Jake Schincariol · MIT · Jakeschincariol/seed-skill

Similar skills

All skills for Finance and business →

From the same set12

The whole set →
seed-market seed-market — a skill for Claude Code estimates TAM, SAM, and SOM. It activates on market-sizing requests or after /seed-scout, before /seed-model and /seed-plan. CX Codex +1 ★ 197repo stars seed-updates The seed-updates Claude Code skill drafts monthly investor updates with metric changes and a runway calculation. It can also prepare a shorter version for prospects who previously said “not now.” CX Codex +1 ★ 197repo stars seed-deck The seed-deck Claude Code skill turns a business plan into a 10-slide pitch deck. It creates an HTML presentation and checks its content and figures. CX Codex +1 ★ 197repo stars seed-terms The seed-terms Claude Code skill calculates ownership and dilution from SAFE and priced-round terms. It runs when asked to assess a deal or flag clauses for legal review. CX Codex +1 ★ 197repo stars seed-scout The seed-scout Claude Code skill examines competitors’ App Store reviews and groups recurring complaints. It runs for competitor research based on an idea or before drafting a plan and pitch deck. CX Codex +1 ★ 197repo stars seed-model seed-model — a Claude Code skill that builds a 36-month financial model from business assumptions. It runs for questions about runway, break-even, fundraising, or before /seed-plan and /seed-deck. CX Codex +1 ★ 197repo stars seed-investors The seed-investors Claude Code skill finds investors for a startup and scores their fit. It runs on requests to find or rank investors, after /seed-plan and before /seed-closer. CX Codex +1 ★ 197repo stars seed-closer The seed-closer Claude Code skill drafts personalised investor emails and tracks replies through to a booked call. It responds to requests to send outreach, sort replies, or arrange a meeting. CX Codex +1 ★ 197repo stars

Project sponsors

Companies that keep this analytics open