DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to compile a business plan with a computed verdict with Founder Skill

Assemble all the founder files into one plan with a verdict from the numbers.

Who it is forA founder who has run the other skills and needs one business plan to share with a partner, lender or advisor.

The problemPlans written by hand can say a business is viable even when the numbers do not support it.

The outcomefounder/business-plan.md with a verdict of Profitable, Not yet or Incomplete computed from the CFO, panel and capacity figures.

What you need first

  • A Claude account, or Claude Code for plugin install and sub-agents
  • Python 3.8 or newer for the tools (no pip install needed)
  • A project folder where the founder/ files will be written

Steps

  1. Run the earlier steps so that the founder/ folder holds the board, panel, pricing, CFO and ops files.
  2. Run python3 skills/founder-plan/compile.py --dir founder to build the plan.
  3. Open founder/business-plan.md and read the verdict and the reasons behind it.
  4. If the verdict is Incomplete or Not yet, return to the step that is missing or weak and rerun it.

Prompt for your agent

Using the Jakeschincariol/founder-skill repo, run `python3 skills/founder-plan/compile.py --dir founder` and report the verdict (Profitable, Not yet or Incomplete) and the reason for it from founder/business-plan.md. Verify that the verdict comes from the computed checks on unit economics, year 1 profit, break-even against capacity and the share of the panel that buys, and not from prose.

Caveat. Not financial, legal or tax advice, so a professional should confirm permits, trademarks, structure and tax before acting on the plan.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page