Menu

Individual skill

rocket-fuel

0upvotes

Runs Fable 5 and OpenAI Codex as co-founders on the Rocket Fuel operating system. Fable is the Visionary (vision, plan, standards, final review); Codex is the Integrator (filters the plan, executes the build, reports). Context-routed, one entry point, four functions: KICKOFF a new project, CLARITY BREAK to refactor an existing one, SAME PAGE MEETING to pressure-test a plan, BUILD A ROCK to hand Codex a scoped task. Use when the user says /rocket-fuel, wants to start or refactor a project with Codex, wants a plan reviewed by a second model, or wants to delegate a build to Codex.

rocket-fuel/SKILL.md

Read pinned source

Source commit 47dde42974cdd7df11c7c1d89f7d9a11b234b176

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
Yes
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
80
Repository last updated
Jul 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Rocket Fuel: the Visionary/Integrator OS for Fable + Codex

It takes two. One sees the future, one makes it happen. Vision without execution is just hallucination.

## Quick start

The user runs `/rocket-fuel <anything in plain English>`. You detect the function (Phase 0), confirm it in one line, and drive the whole thing. The user makes decisions at exactly three gates: the Grill answers, the deadlock tie-break (rare), and the final commit. Everything else runs itself.

**Guide the user the whole way.** Assume they have never seen this system. After confirming the function, tell them in 2-3 lines which stages are coming and where their three gates are. Announce every stage transition in one line ("Same Page Meeting, round 2: Codex is verifying its round-1 findings were addressed"). When the run ends, list the artifacts that now exist and the single next step. Never go silent for a long Codex call: say what is running and roughly how long it takes before you launch it.

## The Accountability Chart (one person per seat)

| Seat | Held by | Five accountabilities |
|---|---|---|