DEV Community

Deduped
Deduped

Posted on

Build a feature with one /autopilot command in Claude Code

#claude #ai #productivity #opensource

Driving Claude Code through plan, code and QA by hand takes a lot of prompts. oh-my-claudecode (OMC) is a plugin that adds multi-agent orchestration on top: describe a feature once and let staged agents work through it. This is how the README sets it up, and what to check before you trust the result.

Install it as a Claude Code plugin

These are Claude Code slash commands. Enter them one at a time, because pasting both lines at once fails, as the README warns:

/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode
Enter fullscreen mode Exit fullscreen mode

Then:

/plugin install oh-my-claudecode
Enter fullscreen mode Exit fullscreen mode

Run the setup command inside the session:

/omc-setup
Enter fullscreen mode Exit fullscreen mode

If you prefer the npm CLI path instead of the marketplace flow, the README gives:

npm i -g oh-my-claude-sisyphus@latest
Enter fullscreen mode Exit fullscreen mode

npm may print a prebuild-install deprecation warning. The README says it comes from an upstream dependency and has no repo-side fix yet.

Build a feature with /autopilot

Give it a feature in your own words:

/autopilot "build a REST API for managing tasks"
Enter fullscreen mode Exit fullscreen mode

Autopilot runs in stages: plan, build, check. If you want a fixed sequence, the README describes a plan-build-qa profile configured under autopilot.workflows in .claude/omc.jsonc. Whatever profile you pick, review the diff and run the tests before merging. An agent that checks its own work is still an agent checking its own work.

A safer first run is to ask it to stop after the plan:

Install Yeachan-Heo/oh-my-claudecode in Claude Code, run /omc-setup, then /autopilot to build <feature> in this repo. Stop after the plan so I can approve it before execution.
Enter fullscreen mode Exit fullscreen mode

Clarify the idea first with /deep-interview

Agents that start from a vague prompt bake in assumptions you never agreed to. OMC includes a Socratic interview that asks questions and measures clarity across weighted dimensions:

/deep-interview "I want to build a task management app"
Enter fullscreen mode Exit fullscreen mode

Answer the questions, then hand the clarified spec to /autopilot or /team.

Run several agents in parallel

The CLI can spawn tmux worker panes, including workers from other providers:

omc team 2:codex "review auth module for security issues"
omc team 1:claude "implement the payment flow"
omc team status
omc team shutdown
Enter fullscreen mode Exit fullscreen mode

Inside Claude Code the native version is /team 3:executor "fix all TypeScript errors". Native teams need CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS set to 1 in ~/.claude/settings.json. Without it, OMC falls back to non-team execution.

Is it too much?

The README itself says some people find OMC overkill and points to a lighter project by the same author, gajae-code. That is a useful signal. If you only need one agent on one small task, plain Claude Code is fine. OMC pays off when you repeatedly run the same plan, build and review loop, or want parallel reviewers.

What we did not verify

  • We followed the README and have not run this end to end for this post.
  • You need Claude Code installed and a plan that covers the extra usage multi-agent runs consume.
  • Check the repo for newer instructions before you rely on these steps.

The step-by-step version is on our use-case page: build a feature end to end with one /autopilot command. The repo overview is here.

Want the setup commands for 50 AI repos people actually ship with? Get the free AI Repos That Actually Ship pack: https://dedupedai.com/ship-pack/?utm_source=devto&utm_medium=article&utm_campaign=shippack

Top comments (0)