agentleFS
Sign inStart free
JakeschincariolJakeschincariol/founder-skill/skills/founder-plan/SKILL.md

founder-plan

Skill131 starsChanged 37 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 40
  2. Very specific:

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

    line 46
  3. Distinctive:

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

    line 55
  4. Very specific:

    Write founder/one-pager.md for someone deciding in two minutes: the problem, the customer, the offer and price, the numbers table, the …

    line 71
  5. Distinctive:

    If the user wants a PDF or a deck, offer to export the plan, but keep the markdown as the source of truth.

    line 82

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free