mcpField
F
founder-ops

founder-ops

github.com/jakeschincariolProductivity2.1k345 installsUpdated 3w ago
Repository

About founder-ops

A founder-focused skill for turning a business concept and financial assumptions into an operational plan. It covers daily workflows, suppliers, staffing, procedures, tools, local compliance checks, and risks.

Key features

  1. 01Maps daily operating steps and customer-facing tasks
  2. 02Researches suppliers, costs, and purchasing terms
  3. 03Plans staffing, routines, and operating tools
  4. 04Lists local permit and insurance checks
  5. 05Builds a ten-item risk register

Use cases

  1. 01Plan the first day, week, and month of operations
  2. 02Check whether supplier costs differ from financial assumptions
  3. 03Prepare procedures and staffing for planned business volume
  4. 04Identify local permits, insurance, and operational risks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jakeschincariol/founder-skill --skill founder-ops

After installing, type/founder-opsin Claude Code to confirm it loaded.

Details

From the project README

founder-ops

A plan that works on paper fails at 7am on a Monday. This skill makes sure the first day, week and month can actually be run, and that the CFO's numbers include what running it really costs.

Step 1: what the business has to do every day

From founder/idea.md, founder/offer.md and founder/numbers.json, write the daily cycle as a list of steps from first thing to last (for a café: deliveries, prep, open, serve, clean, cash up, order; for an online store: orders in, pick, pack, ship, returns, support). Mark which steps a customer sees.

Step 2: suppliers

For every input in the CFO's variable costs and every piece of equipment: two or three real suppliers the user can contact, their public prices or how to get a quote, minimum orders, lead times and payment terms. Link the sources. Where only a quote will tell, say so and add it to the open questions. If a real price differs from founder/numbers.json, update it and say the CFO should re-run.

Step 3: people

Who does what, when: a weekly rota for the planned volume and for the slow first month. The roles, the hours, and the wage assumption (from the user, or a public source for the local minimum and typical pay, linked). Payroll costs beyond wages vary by country; flag them for the accountant.

Step 4: routines (SOPs)

Short, numbered routines for the moments that make or break the business: opening, the core service or fulfilment, handling a complaint, closing, and a weekly reorder. Each fits on one page someone could follow on their first day.

Step 5: tools

The smallest stack that runs it: payments, point of sale or store, scheduling, bookkeeping, inventory. Real products with their published prices, and why each.

Step 6: licences, permits and insurance

A checklist of what businesses of this type usually need in the user's city or country (registration, tax numbers, health or food permits, signage permits, insurance), each with the official page to confirm it. Say plainly that rules differ by place and change, and the user must confirm each with the authority or a professional. Not legal advice.

Step 7: risk register

The ten things most likely to go wrong (a supplier runs out, a key person is sick, the card terminal fails, a bad review, a slow month), each with how likely, how bad, and the plan.

Output

founder/ops.md, plus updated founder/numbers.json if real costs changed. Next: /founder-launch.

Comments

Markdown supported