← Back to list
⚡

founder-plan Checked

Your business planner. Compiles everything the other founder skills wrote (the board's verdict, t…
⚡ Productivity skills By Jakeschincariol Version v1.0.0 Added 2026-10-12 Updated 2026-10-12 Source ↗
9.2Overall rating
0Views
0Downloads
313Stars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "founder-plan" skill by following the instructions at https://skill123.me/install/founder-plan.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/founder-plan.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 5 KB
📊 Static rating
9.2/10
Trigger
8.0
Structure
8.0
Workflow
10.0
Content
10.0
Engineering
9.0
Security
10.0

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

Your business planner. Compiles everything the other founder skills wrote (the board's verdict, the competitors, the buyer panel, pricing, the offer, the CFO's numbers, marketing, brand, operations and the launch plan) into one business plan with a verdict at the top that is computed from the numbers, never written by hand: Profitable, Not yet (with the failing numbers) or Incomplete. Adds an executive summary and a one-page version for a partner, lender or investor. Use when the user says "write my business plan", "put it all together", "is it profitable", "give me the plan", or at the end of the founder pack.

founder-plan

The last step. One document a founder can act on, or hand to a partner or a

lender, built only from what the pack found.

Tool in this folder:


python3 "${CLAUDE_SKILL_DIR}/compile.py" --dir founder

Documentation

Your business planner. Compiles everything the other founder skills wrote (the board's verdict, the competitors, the buyer panel, pricing, the offer, the CFO's numbers, marketing, brand, operations and the launch plan) into one business plan with a verdict at the top that is computed from the numbers, never written by hand: Profitable, Not yet (with the failing numbers) or Incomplete. Adds an executive summary and a one-page version for a partner, lender or investor. Use when the user says "write my business plan", "put it all together", "is it profitable", "give me the plan", or at the end of the founder pack.

founder-plan

The last step. One document a founder can act on, or hand to a partner or a

lender, built only from what the pack found.

Tool in this folder:


python3 "${CLAUDE_SKILL_DIR}/compile.py" --dir founder

Step 1: see what is there


python3 "${CLAUDE_SKILL_DIR}/compile.py" --dir founder --check

prints the verdict and each check. The checks, all computed:

1. Each unit earns money before fixed costs (founder/numbers.json).

2. Year 1 makes an operating profit.

3. The break-even fits inside capacity, if a capacity was given.

4. Enough simulated buyers buy (founder/panel/results.json; default bar 25%,

change it with --min-buy-rate and say why).

If there are no numbers, the verdict is Incomplete: offer to run /founder-cfo.

List the other missing sections with the skill that fills each. Do not fill a

missing section yourself from guesses.

Step 2: the summary

Write founder/summary.md, half a page, plain words:

  • What the business is and who it is for, in two sentences.
  • The verdict and the three numbers behind it (margin, break-even, year 1).
  • What the buyer panel and the board agreed on, and where they disagreed.
  • The biggest risk and what will be done about it.
  • What the founder needs to start (cash from the CFO, the first test from launch).
  • The one thing to do this week.

If the verdict is Not yet, the summary leads with what has to change and which skill

changes it. Never soften a failing check.

Step 3: compile


python3 "${CLAUDE_SKILL_DIR}/compile.py" --dir founder

writes founder/business-plan.md: title, the verdict and its checks, the key numbers

table, the idea, then every section the pack produced (summary, board, competition,

panel, pricing, offer, numbers, marketing, brand, operations, launch), and what is

not done yet.

Step 4: the one-pager

Write founder/one-pager.md for someone deciding in two minutes: the problem, the

customer, the offer and price, the numbers table, the evidence (panel result,

competitor gap, any real test), what the money is for, and the ask. Same numbers as

the plan, word for word.

Rules

View full documentation
  • The verdict comes from compile.py. Never write Profitable by hand, and never

round a failing number into a passing one.

  • Say once, clearly: the panel is simulated buyers and the numbers are projections;

real customers and real quotes confirm them. Not financial, legal or tax advice.

  • If the user wants a PDF or a deck, offer to export the plan, but keep the

markdown as the source of truth.

Output

founder/summary.md, founder/business-plan.md, founder/one-pager.md. Then give

the user the verdict in one line and the one thing to do this week.

Score breakdown

Trigger
8.0
Clear What (one compiled business plan with computed verdict, one-pager) and When with phrasings ('write my business plan','put it all together','is it profitable') plus end-of-pack hook. No explicit When-Not clause.
Structure
8.0
88-line SKILL.md plus compile.py at skill root rather than scripts/; SECTIONS table doubles as the pack manifest; no redundant files.
Workflow
10.0
Verification-first design: the verdict is computed from contribution, year-1 profit, break-even vs capacity and panel buy rate (threshold adjustable, must be justified). Incomplete verdict routes to the exact skill that fills each missing section; guesses forbidden. Summary must never soften a failing check; one-pager must repeat plan numbers word for word.
Content
10.0
Concise imperative style; copy-pasteable commands including --check and --min-buy-rate; verdict semantics documented in the script docstring.
Engineering
9.0
Valid frontmatter with argument-hint. Script has shebang, stdlib-only + no-network declaration. Deduction: importlib load of ../founder-cfo/unit_economics.py only resolves when the sibling skill is installed.
Security
10.0
Capability manifest: reads the founder/ tree (numbers.json, panel/results.json, section markdown); writes founder/business-plan.md and indirectly summary.md/one-pager.md via the agent; no network (grep-verified); no credentials; no persistence. The importlib dynamic load is a declared local sibling-file reuse, not remote code fetch. Capabilities match declared scope.
Pack compiler: compile.py (stdlib-only) computes a verdict (Profitable / Not yet / Incomplete) from four numeric checks including reusing founder-cfo's analyser, and assembles all pack sections into one business plan with a 'not done yet' routing list. Rule 'never write Profitable by hand' is an excellent anti-bias gate. Weakness: imports ../founder-cfo/unit_economics.py, a cross-skill path that breaks standalone; compile.py at skill root instead of scripts/.