agentleFS
Sign inStart free
JakeschincariolJakeschincariol/whale-skill/launch-planner/SKILL.md

launch-planner

Skill15 starsChanged 6 days agoMITView on GitHub

Launch Planner. Plans the launch once it is paid for. Works backwards from the earliest date you promised a paying customer: requirements confirmed, feature complete, customers testing, fixes, first ship, then the rest. The public launch comes last, behind a gate that stays closed until someone has the product, nobody is late, and everything they paid for is built. Use when the user says "launch plan", "when do we launch", "are we on track", "what's next", "plan the launch", "can we launch yet", "launch checklist", or once customers have paid.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. dipaulavs/ClaudeCode-Workspace-2025★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    25 days before: every paying customer confirms the requirements (/requirements confirm).

    line 31
  2. Very specific:

    When a customer has it, /pre-sale deliver, and check in after a week.

    line 45
  3. Very specific:

    Before anything public, launch.py gate.

    line 46
  4. Distinctive:

    Lead with the case study,: not with features.

    line 61
  5. Distinctive:

    Never plans a launch before anyone has paid.

    line 75
  6. Distinctive:

    Never opens the gate over a late or unfinished customer.

    line 76
  7. Distinctive:

    Never posts, sends or spends anything by itself.

    line 77
  8. Distinctive:

    Never invent a number, a result, a client or a deadline.

    line 83

≈ “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

launch-planner

The usual order is build, launch, then hope. Here it's the other way round: paid, built, delivered, and only then launched. By launch day you have customers, a real story and no reason to spend money on ads. This skill plans the weeks in between, around the only dates that matter: the ones you promised.

${CLAUDE_SKILL_DIR} below is this skill's folder (where this SKILL.md lives).

python3 "${CLAUDE_SKILL_DIR}/launch.py" plan --today 2026-11-05
python3 "${CLAUDE_SKILL_DIR}/launch.py" status --today 2026-11-20
python3 "${CLAUDE_SKILL_DIR}/launch.py" gate --today 2026-12-20

The plan

Counted back from the first date you promised:

  • 25 days before: every paying customer confirms the requirements (/requirements confirm).
  • 10 days before: feature complete, everything on the build list.
  • 7 days before: each customer tests it on their own data, with you watching.
  • 2 days before: fix what they found. If anything will slip, tell them now (/pre-sale notice).
  • The day: ship to the first customer, then each of the others by their own date.
  • 14 days after the last one: the public launch, if the gate is open.

plan writes whale/launch-plan.md. A step whose date has already passed is marked to do first. If the dates don't fit what's on the build list, say so today: talk to the customers, not the calendar.

Steps, every Monday

  1. launch.py status. Features built, what's next, and days left for each customer.
  2. /pre-sale due. Anything SOON or LATE is this week's top job.
  3. When a customer has it, /pre-sale deliver, and check in after a week. Once they've seen a result, /case-study.
  4. Before anything public, launch.py gate.

The gate

gate stays CLOSED until all of this is true, and says what's in the way:

  • At least one customer has the product.
  • Nobody is late. Deliver, agree a new date, or refund them first.
  • Everything paying customers asked for is built.

Why so strict: the customers who paid first took the risk. A public launch while one of them is waiting is how you lose them, and they're your best proof.

Launching, when it opens

  • Tell the first customers first, and thank them. Ask if you can name them (/case-study).
  • Lead with the case study, not with features.
  • Go where your buyers are: the trade group, the forum, the newsletter you found in /market-researcher.
  • Pitch the next whales. You can now say something you couldn't before: a real company uses this, and here's what changed.
  • Keep the pre-sale honest. New customers get the real product at the real price. The founding price was for the risk they didn't take.

Posting, emailing and spending on a launch are all the user's calls, one at a time.

Example from the reel's board

Three paying customers on Nov 5, $54,000.00 in. First promise Dec 3. Plan: requirements confirmed by Nov 8, feature complete Nov 23, customers testing Nov 26, fixes Dec 1, ship Dec 3, Dec 4 and Dec 5, public launch Dec 19. gate today: CLOSED, no customer has the product yet. (Illustrative: every company and date is fictional.)

What it never does

  • Never plans a launch before anyone has paid. The plan starts when the money does.
  • Never opens the gate over a late or unfinished customer.
  • Never posts, sends or spends anything by itself.

Consent and truth

  • Nothing is sent, published or charged without the user's explicit yes for that exact message or post. One yes per message. Never "yes to all".
  • A date you promised is a promise. If it will slip, the customer hears it from you first, with their money back on offer.
  • Never invent a number, a result, a client or a deadline. Launch claims must be things you can back up.

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