turbo

Turbo gives Claude Code and Codex a repeatable development process, packaged as Markdown skills. Use a skill for a single task, or combine them into a workflow that takes a change from idea to pull request.

Claude Code: production-tested · Codex: experimental, with skill parity but less real-world use

Get started · What you can do · Browse the guides

From Idea to Pull Request

Plan  →  Implement  →  Finalize

Start with a change you want to make:

/turboplan add password reset to the app

Turbo assesses the scope and helps you settle the approach. Clear-scope changes proceed to implementation after you agree on the shape. When the approach needs a written plan, Turbo drafts and reviews one; you then run /implement-plan in a fresh session.

Once a plan's steps are complete, /finalize runs checks, reviews and polishes the changes, updates documentation and the changelog, captures lessons, and takes you through shipping. For work without a plan file, /implement offers full finalization, a quicker close, or stopping. You can also run /finalize on work you built yourself.

Examples use Claude Code's /skill-name syntax. In Codex, use $skill-name:

$turboplan add password reset to the app

Get Started

Paste this into Claude Code or Codex:

Walk me through the Turbo setup. Read SETUP.md from the tobihagemann/turbo repo and follow the guide for your edition.

The agent selects your edition, installs the skills, and walks you through tools and configuration interactively.

Prefer to read the steps first? Open the Claude Code setup or Codex setup guide.

Pipeline workflows are context-heavy. Peer review uses the other coding agent, so access to both gives you the full workflow. You can replace those review skills to suit your setup. See access and prerequisites for details.

What You Can Do

You can start with any of these skills; you don't need to learn the whole pipeline first.

Skills also work naturally in a request: tests are failing in the auth module, can you please /investigate?

See more prompt examples for dependency updates, UI testing, PR feedback, and other everyday tasks.

Why Turbo

• A process you can repeat. Planning, investigation, review, and shipping workflows are written down as skills, so you can invoke them without rebuilding the prompt each time. They use your project's existing tests, linters, formatters, and hooks.
• Pieces you can replace. Use individual skills or compose them into larger workflows. Swap review tools, commit conventions, or code-style guidance for your own. The skills are plain Markdown using the harness's native tools.
• Lessons carried forward. /self-improve captures corrections and project conventions in instructions, memory, and skills, so future sessions can build on what you've learned.

You stay involved in choosing the approach and reviewing the result. Turbo works best alongside the checks and engineering judgment you already bring to a project.

Go Deeper

• Workflow guide — planning and finalization diagrams, self-improvement, audits, and onboarding.
• Browser and UI testing — hands-on verification and trying changes yourself.
• Customization and setup details — swap skills, understand harness instructions, and update your installation.
• Prompt examples — requests you can copy into your next session.
• All skills: Claude Code index · Codex index — descriptions and dependencies for every skill.

If Turbo helps you ship, consider sponsoring my open source work.

Distributed under the MIT License.