launch-roadmap
/launch-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 says "make a launch roadmap", "I want to launch in 7 days", "what do I do each day", "launch timeline", "plan my launch week", or after /launch-verdict or /launch-improve.
- Author
- Gihonix ↗
- Repository
- production-ready-skill ↗
- Licence
- MIT
- Last repository change
- 04.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: roadmap.py
What it does and when to use it
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 says "make a launch roadmap", "I want to launch in 7 days", "what do I do each day", "launch timeline", "plan my launch week", or after /launch-verdict or /launch-improve.
Triggers from the description
Arguments
/launch-roadmap [days until launch] [project folder]
Original author description
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 says "make a launch roadmap", "I want to launch in 7 days", "what do I do each day", "launch timeline", "plan my launch week", or after /launch-verdict or /launch-improve.
How it works
- Step 1: ask for the duration
- Step 2: build the plan
- Step 3: tell the owner what it means
- Step 4: show it
- Rules
- Output
SKILL.md preview
---
name: launch-roadmap
description: >-
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 says "make a launch roadmap", "I want to launch in 7 days", "what do
I do each day", "launch timeline", "plan my launch week", or after /launch-verdict
or /launch-improve.
argument-hint: "[days until launch] [project folder]"
---
# launch-roadmap
A verdict says where you stand. A roadmap says what to do on Monday.
Writes `launch/roadmap.json` and `launch/roadmap.md`. Read-only on the project's code.
## Step 1: ask for the duration
Ask these, in one message, and wait:
1. **How many days until you want to launch?** Count Launch Day itself: "7" means six
preparation days and Launch Day on the seventh. Accepts 1 to 90.
2. **How many hours a day can you realistically work on it?** Default 4.
3. **Do you have a date for Day 1?** Optional; with it the roadmap shows real dates.
If the argument already gives the days, do not ask again; still confirm hours.
If `launch/verdict.json` is missing, say the plan will have no audit behind it and offer
to run `/launch --quick` first. Run the plan anyway if the owner says so.
## Step 2: build the plan
```bash
python3 "${CLAUDE_SKILL_DIR}/roadmap.py" . --days <N> --hours <H> [--start YYYY-MM-DD]
```
It reads `findings.json`, `logic.json`, `improve.json` and `verdict.json`. Every open
item (FAIL or UNKNOWN) becomes a task with a time estimate, blockers first. The shape
of the plan is fixed and the script does the scheduling, not you:
| Day | Purpose |
| --- | --- |
| Day 1 to Day N-4 | Preparation: close blockers, then business gaps, then should-fix |
| Day N-3 (when N is 4 or more) | Go-live checks: domain, production variables, live payments, email DNS, monitoring, spend caps |
| Day N-1 (when N is 2 or more) | Rehearsal: freeze, restore a backup, roll back once, smoke test, strangers sign up cold |
| **Launch Day** | Go/no-go gate, deploy, smoke test, announce small then wide, watch the first hour |
Blockers are never pushed past launch. If they do not fit, the plan runs over capacity
and a warning says by how much. Should-fix and nice-to-have items that do not fit are
listed as "moved to after launch". Do not reshuffle the output by hand; to change the
plan, change the days, the hours or the findings and re-run.
## Step 3: tell the owner what it means
In plain words, not the whole file: how many days, what Day 1 starts with, whether it
fits, and any warning (over capacity, a one-day plan, no audit). If it does not fit,
give the two honest choices: add days or hours, or launch smaller (a private beta)
with the named blockers open.
## Step 4: show it
The visual template is fixed and already approved (designed once in OpenFrame, now
built into `launch-report`). Do not use OpenFrame or any design tool for a normal run.
```bash
python3 "${CLAUDE_SKILL_DIR}/../launch-report/report.py" .
```
This adds a "Launch roadmap" panel to `launch/report.html`: a header with hours per
day, one row per day with tickable tasks, a rehearsal row, a timed Launch Day run
sheet and an after-launch strip. Tell the owner where to open it.
Only if the owner explicitly asks for a different look, change the template in
`report.py` (and, if they want to see it first, mock it up in a design tool they
name). That is a one-off request, not part of the skill.
## Rules
- Never schedule Launch Day on top of an open blocker silently: the warning stays.
- Never run deploy, DNS or payment commands. Launch Day tasks are the owner's to do.
- Do not invent tasks that the audit and the fixed plan do not contain. Extra advice
goes to `launch-improve`.
- Estimates are rough and assume one person; say so.
## Output
`launch/roadmap.json`, `launch/roadmap.md`, and the roadmap section of
`launch/report.html`.
Files in this package (2)
- SKILL.md 4 KB
- roadmap.py 13 KB
Versions
The database has no other skills named launch-roadmap.
Database snapshot: 13.11.2026 · package version ded170435e81 (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
- 95memstack-marketing-launch-plan
Use this skill when the user says 'launch plan', 'product launch', 'go-to-market', 'launch calendar', or needs a day-by-day launch timeline with pre-launch, launch week, and post-launch task checklists. Do NOT use for ongoing funnel design or ad copy alone. - 100founder-launch
Your launch lead. Builds a dated, step-by-step launch plan: a cheap real-world test first (a waitlist, a pre-sale or a pop-up with a real price, so real buyers confirm what the simulated panel said), then the countdown to opening day with owners and deadlines, the launch-day run… - 100prove-it
Your launch lead. Builds a dated, step-by-step launch plan: a cheap real-world test first (a waitlist, a pre-sale or a pop-up with a real price, so real buyers confirm what the simulated panel said), then the countdown to opening day with owners and deadlines, the launch-day run… - 90launch-war-room
Runs a 7-day launch countdown with a daily plan, owners, launch-day run sheet, metrics and a post-launch review. Use when the user is launching a product, feature or campaign soon, or says 'we launch next week'. - 100founder-launch
Your launch lead. Builds a dated, step-by-step launch plan: a cheap real-world test first (a waitlist, a pre-sale or a pop-up with a real price, so real buyers confirm what the simulated panel said), then the countdown to opening day with owners and deadlines, the launch-day run… - 90launch-playbook
Produces a launch checklist and sequencing plan for a product, calibrated to its GTM motion. Reads business context and GTM spec. Covers pre-launch, launch day, and 30-day post-launch. Use when preparing to ship or announce a product.