Rocket Mode
/rocket-mode
Turn it on and describe the task in plain language. It picks a playbook (Map first, Prove, Drift, Ship, Fix fail or Ground control), routes to the other skills and insists on proof before “done”.
rocket-stack is an open-source skill pack for AI coding agents. Before your agent calls a task done, it writes a short test plan, reviews its own diff, runs the feature for real (UI, API or CLI) and saves the evidence in your repo.
Tested with Cursor · Claude Code Should work with any agent that supports SKILL.md skills.
› /rocket-mode
› add login rate limiting
Playbook: Ship → implement, review, prove
# Mission Log
Playbook: Ship
Next: /pre-flight-check login → /mission-control login
Result: Pass
Proof: mission-map/login/proof/pre-flight.md
mission-map/login/proof/dashboard.png
Note: Rate limit added; Pre-Flight Check Go; login Test Flight passed.
The problem
Agents often mark work as done without showing that it works.
The fix
rocket-stack makes proof part of “done”: no Test Flight, no proof, not done.
Turn on Rocket Mode and describe the task like you would to a teammate. It picks the right playbook and routes every change through the same five stages.
A short test plan per feature: how to reach it, how to control it, and what proof looks like. Kept in sync with the code.
/create-mission-mapYou type the task in plain language. Rocket Mode picks the playbook and hands the work to the right skills.
/rocket-modeThe agent reviews its own diff like a strict peer. Six checks, every finding with file:line. Go or No-go.
The agent runs one real user action on the real surface (a UI, an API or a CLI) to prove it works.
/mission-controlProof saved in your repo: the action, the result and the side effect. Pass or Fail, with the path.
mission-map/<name>/proof/file:line.Start with Rocket Mode and let it route, or call any skill directly. Each one writes only to its own folder and reports in a fixed format.
/rocket-mode
Turn it on and describe the task in plain language. It picks a playbook (Map first, Prove, Drift, Ship, Fix fail or Ground control), routes to the other skills and insists on proof before “done”.
/mission-control <name>
Proves one mission: updates its Mission Map if needed, runs a Test Flight and leaves a Mission Log. On a fail it still captures proof when possible.
/create-mission-map
Interviews the repo, writes the top 3–5 missions (happy paths first, then auth, then fragile flows) and proves one with Mission Control.
/maintain-mission-map
Fixes drift when routes, commands, selectors or flows change. Keeps every existing proof file and lists the missions that need a new proof.
/pre-flight-check <name>
Reviews its own diff like a strict peer, before the Test Flight. Brief, Tests, Errors, Security, Readability, Debris: every finding with file:line. Any Open means No-go.
/ground-control
Repo-wide, outside the five-stage flow: run it anytime. Scans for duplicates, dead code, missing tests, oversized files, fragile code and debris, keeps a Space Debris list with a trend and picks the top 1–3 to fix next. It never changes app code.
Maps and proof live in the target repo, next to the code, not in the skill pack. Anyone on the team can open them and check.
Markdown, screenshots and command output under mission-map/. Commit them and they show up in code review like any other change.
Review findings and debris items cite file:line. No evidence, no item.
Proof is never deleted, and Space Debris items are never removed, only marked Fixed or Accepted.
Change: Rate limit on POST /api/login
| Check | Status | Evidence |
|---|---|---|
| Brief | Pass | src/auth/login.ts:42 — 5 attempts/min per IP, as asked |
| Tests | Fixed | test/login.test.ts:88 — added test for 429 after 5 attempts |
| Errors | Pass | src/auth/login.ts:51 — limiter store down → request allowed, error logged |
| Security | Pass | src/auth/login.ts:44 — keyed by IP, no email in logs |
| Readability | Pass | None |
| Debris | Fixed | src/auth/login.ts:60 — removed console.log |
Replaced on every run, so it always reviews the final code.
Surface: UI
Allows a user to sign in with email and password.
Open the app and go to /login.
1. Enter email and password
2. Click Login
Selector: [data-testid="login-button"]
Screenshot of the dashboard after redirect (proof/dashboard.png).
- Invalid credentials must show an error
The proof matches the surface:
Last scan: 2026-11-21 · Open: 2 (was 3) · Trend: better
| ID | Type · Severity · Evidence | Status |
|---|---|---|
| D1 | Duplicate · Mediumsrc/auth/login.ts:30, src/auth/signup.ts:28 — same email validation | Open |
| D2 | Missing tests · Highsrc/billing/invoice.ts:12 — no test for invoice totals | Open |
| D3 | Debris · Highsrc/app.ts:88 — console.log of request body | Fixed |
| D4 | Oversized · Lowsrc/admin/panel.tsx:1 — 900 lines | Accepted |
Next: D2 add tests for invoice totals · D1 share email validation
No build step and no config. Each skill is a plain folder with a SKILL.md your agent reads.
Clone the repo and copy the six skill folders into your personal Cursor skills folder, so they work in every project:
git clone https://github.com/rocketbase-space/rocket-stack.git
cd rocket-stack
mkdir -p ~/.cursor/skills
cp -R rocket-mode mission-control create-mission-map \
maintain-mission-map pre-flight-check ground-control \
~/.cursor/skills/One project only? Copy them to .cursor/skills/ in your repo root instead and commit them, so your team gets them too.
Clone the repo and copy the six skill folders into your personal Claude Code skills folder, so they work in every project:
git clone https://github.com/rocketbase-space/rocket-stack.git
cd rocket-stack
mkdir -p ~/.claude/skills
cp -R rocket-mode mission-control create-mission-map \
maintain-mission-map pre-flight-check ground-control \
~/.claude/skills/One project only? Copy them to .claude/skills/ in your repo root instead and commit them, so your team gets them too.
Copy the six skill folders into the directory your agent loads skills from. Each folder holds one SKILL.md.
git clone https://github.com/rocketbase-space/rocket-stack.git
cd rocket-stack
cp -R rocket-mode mission-control create-mission-map \
maintain-mission-map pre-flight-check ground-control \
<your-agent-skills-dir>/Not tested yet, but it should work with any agent that supports SKILL.md skills. Check your agent’s docs for its skills folder.
Enable Rocket Mode, then type the task as a normal message. No flags, no forms.
› /rocket-mode › add login rate limiting
Or call a skill directly:
/mission-control login
/create-mission-map
/maintain-mission-map
/pre-flight-check login
/ground-control
mission-map/<name>/README.mdOne Mission Map per mission, in Markdown.mission-map/<name>/proof/Screenshots, responses or output, plus pre-flight.md (replaced on each run). Proof is never deleted.ground-control/debris.mdOnly when you run /ground-control.It asks at most three questions per run; otherwise it notes its assumptions and carries on.
Give your agent the same standard you would give a teammate: show it works, then call it done.