Day-One Operations Planner

Founder ops

by Jakeschincariol · MIT license · ★ 322 on GitHub

Your operations manager. Works out how the business actually runs on day one: suppliers and what they cost, who works when, the step-by-step routines for opening, serving or shipping and closing, the tools to run it, the licences and…

---
name: founder-ops
description: >-
  Your operations manager. Works out how the business actually runs on day one:
  suppliers and what they cost, who works when, the step-by-step routines for
  opening, serving or shipping and closing, the tools to run it, the licences and
  permits to check, and a risk register with what to do when each thing goes
  wrong. Feeds real costs back to the CFO. Use when the user says "how do I run
  this", "operations", "suppliers", "staffing", "SOPs", "what do I need to open",
  "permits", or "day one".
argument-hint: "[city or country]"
---

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

Overview

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.

Manual install (npx, ZIP)

Claude Codenpx skills add Jakeschincariol/founder-skill --skill founder-ops -g -a claude-code

Claude Code (degit)npx degit Jakeschincariol/founder-skill/skills/founder-ops#main ~/.claude/skills/founder-ops

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md3.0 KB

Read SKILL.md here

Jakeschincariol/main1 file shown

SKILL.md3.0 KB

Browse every file on GitHub↗

SKILL.md

Show the full text71 lines

founder-ops/SKILL.md71 lines · 3.0 KB

PreviewCode

Outline

RawView on GitHub

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.

1	---
2	name: founder-ops
3	description: >-
4	Your operations manager. Works out how the business actually runs on day one:
5	suppliers and what they cost, who works when, the step-by-step routines for
6	opening, serving or shipping and closing, the tools to run it, the licences and
7	permits to check, and a risk register with what to do when each thing goes
8	wrong. Feeds real costs back to the CFO. Use when the user says "how do I run
9	this", "operations", "suppliers", "staffing", "SOPs", "what do I need to open",
10	"permits", or "day one".
11	argument-hint: "[city or country]"
12	---
13
14	# founder-ops
15
16	A plan that works on paper fails at 7am on a Monday. This skill makes sure the
17	first day, week and month can actually be run, and that the CFO's numbers include
18	what running it really costs.
19
20	## Step 1: what the business has to do every day
21
22	From `founder/idea.md`, `founder/offer.md` and `founder/numbers.json`, write the
23	daily cycle as a list of steps from first thing to last (for a café: deliveries,
24	prep, open, serve, clean, cash up, order; for an online store: orders in, pick,
25	pack, ship, returns, support). Mark which steps a customer sees.
26
27	## Step 2: suppliers
28
29	For every input in the CFO's variable costs and every piece of equipment: two or
30	three real suppliers the user can contact, their public prices or how to get a
31	quote, minimum orders, lead times and payment terms. Link the sources. Where only
32	a quote will tell, say so and add it to the open questions. If a real price
33	differs from `founder/numbers.json`, update it and say the CFO should re-run.
34
35	## Step 3: people
36
37	Who does what, when: a weekly rota for the planned volume and for the slow first
38	month. The roles, the hours, and the wage assumption (from the user, or a public
39	source for the local minimum and typical pay, linked). Payroll costs beyond wages
40	vary by country; flag them for the accountant.
41
42	## Step 4: routines (SOPs)
43
44	Short, numbered routines for the moments that make or break the business: opening,
45	the core service or fulfilment, handling a complaint, closing, and a weekly
46	reorder. Each fits on one page someone could follow on their first day.
47
48	## Step 5: tools
49
50	The smallest stack that runs it: payments, point of sale or store, scheduling,
51	bookkeeping, inventory. Real products with their published prices, and why each.
52
53	## Step 6: licences, permits and insurance
54
55	A checklist of what businesses of this type usually need in the user's city or
56	country (registration, tax numbers, health or food permits, signage permits,
57	insurance), each with the official page to confirm it. Say plainly that rules
58	differ by place and change, and the user must confirm each with the authority or a
59	professional. Not legal advice.
60
61	## Step 7: risk register
62
63	The ten things most likely to go wrong (a supplier runs out, a key person is sick,
64	the card terminal fails, a bad review, a slow month), each with how likely, how
65	bad, and the plan.
66
67	## Output
68
69	`founder/ops.md`, plus updated `founder/numbers.json` if real costs changed. Next:
70	`/founder-launch`.
71