Who it is forA Claude Code user who wants to describe a feature once and let the agents handle the steps.
The problemDriving Claude Code through planning, coding and QA by hand takes many prompts.
The outcomeA feature built through OMC's staged autopilot, with an optional plan, build and QA profile.
What you need first
- Claude Code
- npm for the CLI path (oh-my-claude-sisyphus)
- tmux and the Codex or Gemini CLIs for terminal team workers
- Linux with flock for named autopilot stage profiles
Steps
- In Claude Code run
/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode, then/plugin install oh-my-claudecode(one at a time) - Run /omc-setup inside the session
- Run
/autopilot "build a REST API for managing tasks"with your own feature - For a fixed sequence, configure a plan-build-qa profile under autopilot.workflows in .claude/omc.jsonc
- Review the result and the tests before merging
Prompt for your agent
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.
Caveat. This card is written from the Yeachan-Heo/oh-my-claudecode README, not from a test run by Deduped. Before you start, make sure you have Claude Code. Check the repo for newer instructions before you rely on these steps.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for Yeachan-Heo/oh-my-claudecode and "Build a feature end to end with one /autopilot command"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer