agentleFS
impactbrusselsimpactbrussels/FounderOS/skills/legal-and-incorporation/SKILL.md

legal-and-incorporation

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Use when a founder is forming the company or worried they've skipped legal basics - when they ask "should I incorporate", "when do I form a company", "LLC or C-corp or what", "do I need a founders' agreement", "how do I assign IP to the company", "what's founder vesting", "is my cap table clean", "what contracts do I need early", or are taking money/hiring/launching on a handshake. Covers whether/when to incorporate, entity-type concepts, founder IP assignment, vesting, clean records, and early contracts. General legal EDUCATION - NOT legal advice; rules vary by jurisdiction; hire a local lawyer.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Incorporate decision: do it now or wait, with the trigger that decides it - flagged "confirm timing/cost with local lawyer."

    line 85
  2. Distinctive:

    Prefer a lawyer-reviewed document over a downloaded template wherever money, equity, IP, or employment is involved.

    line 97

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Legal and Incorporation

This is general legal education, NOT legal advice. Nothing here is a recommendation for your situation. Company law, tax, securities, employment, and IP rules vary enormously by country and by state/province, change over time, and depend on facts this skill can't see. Do not rely on any threshold, rate, entity name, or "standard" mentioned here as fact - they are illustrative concepts to discuss. Before you act, confirm the specifics with a qualified lawyer (and accountant) licensed in your jurisdiction. A few hundred spent on a startup lawyer early is the cheapest insurance against mistakes that are expensive - or impossible - to unwind later.

Most legal mistakes founders make are invisible for years, then fatal exactly when it matters most - at the first hire, the first investor, the first acquisition, or the first co-founder falling out. The asymmetry is brutal: the right setup costs a little now; the wrong setup can kill a fundraise or a sale later. This skill gets the foundations right early, when they're cheap, and tells you precisely where you must stop guessing and call a lawyer.

The method

Built on the Founder OS scaffold (High tier). Full checklist, entity concepts, and the irreversible-mistakes list in references/incorporation-basics.md.

Step 1 - Decide whether and when to incorporate (research before asserting)

Incorporating creates a separate legal person that can own IP, sign contracts, take investment, and shield your personal assets - but it also brings cost, filings, and reporting. Common triggers to incorporate: you're taking outside money, hiring, signing meaningful contracts, holding valuable IP, or working with a co-founder. When and whether depends on your jurisdiction's rules - research the trigger points and costs locally, and confirm with a lawyer before filing. Don't incorporate prematurely "to feel real"; don't delay it past the first co-founder or first dollar of investment.

Step 2 - Choose an entity type at the concept level (a draft is not a decision)

Compare entity options on the dimensions that actually matter (concepts in the reference): liability protection, tax treatment, investor-readiness, and admin burden. Different structures suit a lifestyle business, a bootstrapped company, and a venture-backed startup. Form a shortlist and a leaning - then have a qualified local lawyer/accountant confirm the right vehicle for your goals and country. The entity name that's "standard" for fundable startups differs by jurisdiction; never assume.

Step 3 - Assign founder IP to the company

This is the one founders regret most. Whatever you (and any contractor, designer, or early collaborator) created for the startup - code, designs, brand, content - must be legally assigned to the company in writing. Verbal "it's the company's" is not assignment. Missing IP assignments routinely blow up due diligence and can sink a fundraise or acquisition. Get proper assignment agreements drafted/reviewed by a lawyer.

Step 4 - Set up founder vesting (ALWAYS)

Vesting means founders earn their equity over time (commonly with a cliff), so that a founder who leaves in month three doesn't walk away owning a large slice forever. It protects the people who stay and is expected by investors. Always vest founder equity, including your own. The exact schedule and mechanics vary by jurisdiction and tax treatment - set them with a lawyer, but never skip vesting.

Step 5 - Keep a clean cap table and records (batch then decide)

Maintain a single, accurate cap table (who owns what), signed equity documents, board and decision records, and the founders' agreement. Sloppy or contradictory records are a classic deal-killer in diligence. Batch the foundational documents and have them reviewed together rather than papering over gaps later.

Step 6 - Know which contracts matter early (ask before assuming)

A short list of agreements does most of the protective work early: founders' agreement, IP assignments, customer/supplier terms, an NDA where genuinely warranted, and proper contractor/employee paperwork. Identify which you actually need now versus later - and where a template is fine versus where you must have a lawyer draft or review. When unsure, ask the lawyer; don't assume a downloaded template fits your jurisdiction.

Output

  • Incorporate decision: do it now or wait, with the trigger that decides it - flagged "confirm timing/cost with local lawyer."
  • Entity shortlist + leaning, compared on liability / tax / investor-readiness / admin - explicitly marked as a draft to confirm with a lawyer.
  • IP assignment plan: who created what, what must be assigned, and that a lawyer will paper it.
  • Vesting plan: confirmed you'll vest all founders (schedule TBD with counsel).
  • Records to stand up now: cap table, founders' agreement, equity docs, the early-contract shortlist.
  • The "call a lawyer now" list: the specific items you will not DIY.

Constraints

  • Never state a legal threshold, tax rate, filing rule, or "standard" entity as settled fact. Flag it and route to a local lawyer.
  • Stay jurisdiction-agnostic. Concepts and questions, not country-specific rules. The founder supplies the country; the lawyer supplies the law.
  • Always vest. Always assign IP in writing. These two get founders into the most expensive trouble.
  • Prefer a lawyer-reviewed document over a downloaded template wherever money, equity, IP, or employment is involved.
  • A clean cap table and signed docs are not bureaucracy - they're what survives due diligence. Build them early.

Copy-paste version

Act as a clear, practical startup-formation guide for a first-time founder.
VERY IMPORTANT: this is general education, NOT legal or tax advice. Rules vary by country/state and change over time. Never tell me a specific legal threshold, tax rate, or entity is correct as fact - flag every such point and tell me to confirm it with a qualified lawyer/accountant in my jurisdiction before acting.
My startup: [ONE_LINER]. Stage: [STAGE]. My country/state: [tell me to fill this in]. Constraint: [CONSTRAINT].
Walk me through:
1. Whether and WHEN I should incorporate, based on triggers (taking money, hiring, IP, co-founder) - and tell me to confirm timing and cost locally.
2. Entity-type CONCEPTS compared on liability, tax, investor-readiness, and admin burden - give me a shortlist and a leaning, marked as a draft to confirm with a lawyer.
3. How to make sure all founder/contractor IP is legally assigned to the company in writing, and why this matters at diligence.
4. Why I must set up founder vesting (including my own) and what it protects - note the schedule needs a lawyer.
5. What clean records to stand up now: cap table, founders' agreement, equity docs.
6. Which contracts actually matter early, and where a template is risky vs. where I must hire a lawyer.
End with my "call a lawyer now" list - the specific things I should NOT DIY.

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.