smokejumper

SmokeJumper

A drop-in, autonomous product-development crew packaged as a standalone plugin for Claude Code and Codex.

SmokeJumper lands cold in any repo, builds a model of what exists, decides the highest-leverage next move itself, executes via a mix of Claude agents and Codex, gates every push through an adversarial review, and runs a lessons-learned pass at the end — enriching both the target repo's own knowledge store and the plugin itself. Two things compound per deployment: the repo gets better, and the crew gets sharper.

---

SmokeJumper installs from the same plugin manifest in both runtimes — Claude Code and Codex share the SKILL.md + agents/ + .claude-plugin/marketplace.json format.

Claude Code

From GitHub:

claude plugin marketplace add https://github.com/shanemhamilton/smokejumper
claude plugin install smokejumper@smokejumper

Or from a local checkout (swap the marketplace source):

claude plugin marketplace add ~/Documents/SmokeJumper
claude plugin install smokejumper@smokejumper

Codex

codex plugin marketplace add shanemhamilton/smokejumper

Then install the smokejumper plugin from within Codex (its skill-installer handles enablement). For a local checkout, point the marketplace at the directory instead:

codex plugin marketplace add ~/Documents/SmokeJumper

Validate / release (Claude Code)

Validate before installing:

claude plugin validate ~/Documents/SmokeJumper

Cut a versioned release tag:

claude plugin tag ~/Documents/SmokeJumper

---

Usage

/smokejumper

Starts a full sprint. SmokeJumper proceeds through all eight phases autonomously, pausing only for decisions that require product strategy, budget authority, or explicit release sign-off.

---

Running under a Codex (or non-Claude) orchestrator

SmokeJumper is built for Claude Code, but it also runs when a Codex agent (or any file-and-shell capable agent) is the top-level orchestrator — point the agent at skills/smokejumper/SKILL.md and have it follow the eight phases. A runtime preflight (references/runtime.md) detects what your runtime can do and adapts:

• No subagent dispatch → leads and reviewers are adopted inline: the orchestrator reads the resolved agents/*.md persona and acts as that role for the phase. RECON runs scripts/sj scan, which resolves the leads, writes the mapping into repo-knowledge.md + adapter-scan.json, and prints a "Leads established" banner — so lead establishment is a visible, durable artifact, not an implicit step.
• The sj CLI is runtime-agnostic → any orchestrator that can run a shell command gets the same deterministic gates (sj gate), state validation (sj validate-state), and safety tripwires (sj lane-check).
• No Skill tool → the embedded reference files are used directly. Product context is bootstrapped by references/product-context.md + templates/product-context.md with no dependency on any external skill.
• anthropic-skills:handoff-prompt unavailable → Phase 8 writes <target>/.smokejumper/HANDOFF.md directly.
• choo-choo-ralph / bd absent → Lane A is unavailable; all work routes to Lane B (the synchronous crew).

---

Lead establishment & product context

Two RECON outputs are durable, visible artifacts rather than steps an orchestrator has to remember — so they hold up under any runtime, including a Codex agent that skims prose.

Leads are established by a deterministic scan, not from memory. scripts/sj scan resolves the product / engineering / design leads (a project-specific override or the bundled fallback), the gate roles, and the available capabilities; writes the mapping into <target>/.smokejumper/repo-knowledge.md; emits a leads_established event to the sprint log; and prints a banner:

=== SmokeJumper — Leads Established ===
  Product lead:      smokejumper-product-lead   [BUNDLED]
  Engineering lead:  smokejumper-engineering-lead   [BUNDLED]
  Design lead:       smokejumper-design-lead   [BUNDLED]
  Gates resolved:    designReviewer=null thesisGuardian=null reviewIntegrity=null firstUseCritic=null qualityControl=null
  Capabilities:      asyncLoop=no codex=yes metaswarm=no bugsweep=no tracker=beads
  Design skills:     review=design-review consult=design-consultation a11y=accessibility-wcag frontend=frontend-design (plugin)
  Design system:     tailwind.config.js,src/theme.css,.storybook/
  Functional health: HEALTHY  →  design posture: WEIGHTED
  Product context:   MISSING — run Setup before DECIDE
=======================================