Skip to content
Skills Library
Management & product · Review & audit

launch

/launch

Gets an AI-built project to a confident go-live. Understands what the project contains, finds the gaps with evidence, reviews business logic, recommends pricing from competitor data, computes a Ready / Almost / Not yet verdict, fixes what can be fixed safely, and hands over a launch-day runbook and a post-launch watch plan, with a visual report. Use when the user says "am I ready to launch", "launch my app", "is my vibe-coded project production ready", "go live checklist", "what am I missing before launch", "/launch", or starts the launch-ready pack.

Licence
MIT
Last repository change
04.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Gets an AI-built project to a confident go-live. Understands what the project contains, finds the gaps with evidence, reviews business logic, recommends pricing from competitor data, computes a Ready / Almost / Not yet verdict, fixes what can be fixed safely, and hands over a launch-day runbook and a post-launch watch plan, with a visual report. Use when the user says "am I ready to launch", "launch my app", "is my vibe-coded project production ready", "go live checklist", "what am I missing before launch", "/launch", or starts the launch-ready pack.

Triggers from the description

am I ready to launchlaunch my appis my vibe-coded project production readygo live checklistwhat am I missing before launch

Arguments

/launch [--quick] [project folder]
Original author description

Gets an AI-built project to a confident go-live. Understands what the project contains, finds the gaps with evidence, reviews business logic, recommends pricing from competitor data, computes a Ready / Almost / Not yet verdict, fixes what can be fixed safely, and hands over a launch-day runbook and a post-launch watch plan, with a visual report. Use when the user says "am I ready to launch", "launch my app", "is my vibe-coded project production ready", "go live checklist", "what am I missing before launch", "/launch", or starts the launch-ready pack.

How it works

  1. Stages
  2. How to run it
  3. Honest limits (say them once, early)
  4. Rules
  5. Output
Original SKILL.md headings · 67 lines, 604 words
SKILL.md preview
---
name: launch
description: >-
  Gets an AI-built project to a confident go-live. Understands what the project
  contains, finds the gaps with evidence, reviews business logic, recommends pricing
  from competitor data, computes a Ready / Almost / Not yet verdict, fixes what can be
  fixed safely, and hands over a launch-day runbook and a post-launch watch plan, with
  a visual report. Use when the user says "am I ready to launch", "launch my app", "is
  my vibe-coded project production ready", "go live checklist", "what am I missing
  before launch", "/launch", or starts the launch-ready pack.
argument-hint: "[--quick] [project folder]"
---

# launch

The orchestrator for the launch-ready pack. Its job: replace "I hope it's fine" with a
verdict the owner trusts, then a plan for after.

Everything it writes goes to `launch/` in the project. The only stage that edits code
is `launch-fix`, with approval.

## Stages

| # | Skill | Question it answers | Writes |
| --- | --- | --- | --- |
| 1 | `launch-scan` | What did the AI actually build? | `map.md`, `inventory.json`, `context.json` |
| 2 | `launch-gaps` | What is missing or unsafe, with proof? | `findings.json`, `gaps.md` |
| 3 | `launch-logic` | Does the business actually work? | `logic.json`, `logic.md` |
| 4 | `launch-improve` | What business and logic gaps are there, and what would make it better? | `improve.json`, `improve.md` |
| 5 | `launch-pricing` | What should I charge? | `pricing.md`, `pricing.json` |
| 6 | `launch-verdict` | Can I go live? | `verdict.json`, `verdict.md`, `history.json` |
| 7 | `launch-fix` | Fix what you found | commits on `launch-ready/fixes` |
| 8 | `launch-report` | Show me | `report.html` |
| 9 | `launch-roadmap` | What do I do each day until launch? | `roadmap.json`, `roadmap.md`, roadmap panel in `report.html` |
| 10 | `launch-day` | How do I go live safely? | `runbook.md` |
| 11 | `launch-watch` | What do I watch after? | `watch.md`, `monitoring/` |

`--quick` runs stages 1, 2, 6 and 8 only: a verdict and a picture in a few minutes.

## How to run it

1. **Orient** (2 minutes): confirm the project folder, create `launch/` and add it to
   `.gitignore` suggestion (not forced). Ask only what the code can't tell:
   - Who is it for and how many users do you expect in month one?
   - Will it take money? Will it hold personal data (emails, names, files)?
   - Does it call paid APIs (AI, SMS, email)?
   - Where will it be hosted?
2. Run stages in order, invoking each skill (`/launch-scan` and so on). Between stages,
   give the owner one or two plain sentences on what was found. Keep the tone calm:
   most vibe-coded apps have fixable gaps; the point is to see them.
3. After stage 6, stop and show the verdict. Ask what to do next: fix the blockers
   (stage 7), see the report (8), plan the days to launch (9), or go straight to the
   runbook (10).
4. After fixes, re-run stages 2, 4, 6 and 8 so the owner sees the score move.
5. Finish with `launch-roadmap` (ask how many days), `launch-day` and `launch-watch`. End with the one thing to do first
   tomorrow morning.

## Honest limits (say them once, early)

- This reads code and config; it cannot see your dashboards, DNS or live data, so some
  items are "unverified" until you confirm them. Unverified is never counted as passed.
- It is not a penetration test, a security certification or legal/financial advice.
  For handling payments or health/financial data at scale, get a professional review.
- Heuristics can be wrong in both directions; every finding cites where to look.

## Rules

- Evidence or it didn't happen. Never mark something PASS without proof.
- Never print secret values, anywhere.
- Never deploy, never change production, never force-push.
- The verdict is computed by `launch-verdict`; never state one by hand.
- If a stage's skill is not installed, say which one and continue with the rest.

## Output

The `launch/` folder (above) and a closing summary: verdict, readiness and confidence,
what changed this session, what the owner must still do themselves, and the next review
date.

Versions

RepositoryScoreLicence
This page · Gihonix/production-ready-skill90MIT
devdotfast/whiteboard100MIT
microsoft/vscode100MIT
lilly-logic-labs/lll-skills100MIT
workbench-soft/agent-skills100MIT
ADWilkinson/astack100MIT
terrylica/cc-skills100MIT
gn01763009/user-thoughts100MIT
Exxzzent/rocket100MIT

Database snapshot: 13.11.2026 · package version 8ddbfa1847bc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100launch-verdict
    Computes the go/no-go answer for launching: Ready, Almost, or Not yet. The verdict is calculated by a script from the findings, never written by hand, with a readiness score, a confidence score, per-area scores, the top five fixes and a plain answer to "is it safe to…
  • 100workflow-launch-ready
    Launch-preparation sweep for a new app or major release. Use when "prepare for launch", "launch week", "everything before going live", "is the app launch-ready?", or "pre-launch sweep". Working tree to a PR → workflow-release-prep.
  • 100launch-roadmap
    Asks how many days until launch and turns the open audit findings into a day-by-day roadmap: Day 1, Day 2, and so on up to Launch Day, saying what to do each day, how long it takes and when each day is done, and shows it in the report using a fixed template. Use when the user…
  • 90web-launch-checklist
    Run the maintained 192-item web launch checklist and produce an evidence-backed go/no-go record for an exact release. Use when asked to work through a pre-launch checklist, fill a web launch record, or make a checklist-based launch decision. A general whole-repository quality…
  • 100mvp-launch
    Web app MVP launch checklist knowledge. Auto-triggered when conversation involves "launch readiness", "MVP checklist", "production ready", "go live", or pre-launch verification. Provides the 10-point criteria for what counts as "done" in each area. Based on "Realistic MVP Launch…
  • 100crowdstop-launch
    Proves people will pay with a small real-money test, then plans the weeks to launch day, a timed plan for the day and the month after. Use when the user says \"launch\", \"plan my launch\", \"launch checklist\", \"when can I launch\" or \"go live\".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.