PluginInstalls cleanly
Plan features as specs before coding
Conductor
Conductor makes your assistant write a spec and a step-by-step plan for each feature before coding, keeps project context in files and can undo work.
- Works with
- Claude Code
- Good for
- Build an app
What it does
Conductor stops your assistant from jumping straight into code. For each feature or bug fix it works in three steps: context, then spec and plan, then build.
/conductor:conductor-setup(run once) asks about your product, style rules, tech stack and workflow, and saves the answers in aconductor/folder./conductor:conductor-new-track "..."creates a "track" for one feature or fix, with aspec.md(what to build) and aplan.md(phases and tasks) for you to review./conductor:conductor-implementworks through the plan task by task, ticks off each step and commits as it goes. The default workflow writes tests first./conductor:conductor-statusshows progress,/conductor:conductor-reviewchecks finished work against the plan and your guidelines, and/conductor:conductor-revertundoes a track, phase or task using git.
The plugin is six skills. You can type the commands above, or just ask in plain words, for example "Let's start a new track to add a login screen" (README). Because the plan lives in files, you can stop and come back later, and teammates see the same context.
Example prompts
/conductor:conductor-setup/conductor:conductor-new-track "Add a dark mode toggle to the settings page"/conductor:conductor-implement- "How is our track progress going?"
/conductor:conductor-revert(then pick the task you want to undo, and choose Safe)
How to install
/plugin marketplace add gemini-cli-extensions/conductor/plugin install conductorHow to use it
Run /conductor:conductor-setup once in your project, then /conductor:conductor-new-track "Add a dark mode toggle", review the spec and plan, and run /conductor:conductor-implement.
Check it works
Type /conductor: in Claude Code and look for the six commands: setup, new-track, implement, status, review and revert, each starting with conductor-. Run /conductor:conductor-setup in a test project and check that a conductor/ folder appears with files such as product.md, tech-stack.md, workflow.md and index.md.
Common problems
- The commands do not show up — run
/reload-pluginsor restart Claude Code — https://code.claude.com/docs/en/discover-plugins - Token use is higher than expected — the README warns about this; keep tracks small and check usage with
/usagein Claude Code (the README's/stats modelis for other clients) — https://code.claude.com/docs/en/commands - Too many commits in your history — Conductor commits code and plan updates after each task; work on a branch and squash when you merge — https://github.com/gemini-cli-extensions/conductor/blob/main/skills/conductor-setup/assets/workflow.md
- Setup stops early — the setup skill runs a small Python 3 script to see which setup steps are done, so install Python 3 first — https://github.com/gemini-cli-extensions/conductor/blob/main/skills/conductor-setup/SKILL.md
- Extra skills that setup downloaded do not appear — they go to
.agents/skills/, and the Claude Code skills docs list.claude/skills/folders, not that one — https://code.claude.com/docs/en/skills - You want to remove it — run
/plugin uninstall conductor, then/plugin marketplace remove conductor(the marketplace is namedconductor; the README writesgemini-cli-extensions/conductorthere) — https://code.claude.com/docs/en/discover-plugins
Other assistants
- Antigravity:
agy plugins install https://github.com/gemini-cli-extensions/conductor(README). - Gemini CLI: the Gemini CLI extensions gallery gives
gemini extensions install https://github.com/gemini-cli-extensions/conductor. Gemini CLI installs a GitHub link from the latest GitHub release, so you get the older extension v0.4.1 (2026-03-11) with commands such as/conductor:setupand/conductor:newTrack, not the plugin described on this page. The README on main no longer covers Gemini CLI. - Codex: no route in the README.
What to watch out for
- It writes a conductor/ folder into your repo and makes git commits as it works: your code changes, plan updates such as conductor(plan): Mark task '...' as complete, and chore(conductor) commits that start, finish, archive or delete a track. The default workflow also adds a git note to each task commit (skill files, workflow.md)
- No skill sets disable-model-invocation, so Claude can start a Conductor skill from a plain request such as "Start implementing the active plan" (README), and the implement skill commits. No skill sets allowed-tools, so your normal Claude Code permission prompts still apply
- The revert skill asks you to pick Safe (Recommended), which runs git revert, or "Hard Reset (Destructive)", which runs git reset --hard. The skill itself says: "This will lose all uncommitted changes and rewritten history. WARNING: This is destructive and should be used with caution." Pick Safe unless you are sure
- Setup and new-track can suggest extra Firebase or Google Cloud skills and, if you say yes, download their SKILL.md with curl into .agents/skills/. The skill says a third-party skill is installed as a frozen version, but the catalog links point at the main branch of those repos, so you get whatever is there that day
- The README warns: "This can lead to increased token consumption, especially in larger projects or during extensive planning and implementation phases."
- Version numbers are confusing: the Claude Code install takes the newest commit on main (2026-09-01), whose VERSION file says 0.3.0 and whose plugin.json has no version. The GitHub releases, newest v0.4.1 on 2026-03-11, are the older Gemini CLI extension from before the move to a plugin (merged 2026-07-15), so they do not describe what Claude Code installs
Licence and author
- Licence
- Apache-2.0
- Author
- gemini-cli-extensions (Google-hosted project)
- Source code
- github.com/gemini-cli-extensions/conductor
How we tested it
We installed it on an empty test computer on 29 Oct 2026. Installed and started in a clean test system. Not yet used in a real AI session.
The intake sandbox needs the plugin@marketplace form, so it skipped this install line; the bare name worked by hand. No model call, so the skills were not run. Not yet used on real work.
Technical details of the test
- Date
- 29 Oct 2026
- Method
- Manual sandbox run on 2026-10-29 in the intake's clean container with no account: ran "claude plugin marketplace add gemini-cli-extensions/conductor" and "claude plugin install conductor" (installed as conductor@conductor, enabled, 6 skill files, no hooks, no .mcp.json).
Checked again on 29 Oct 2026
Alternatives
- Superpowers — a general plan, test-first and review workflow for Claude Code and Codex
- Planning with Files — keeps a plan, findings and progress in Markdown files while the assistant works
FAQ
- Q: Does it cost money? A: No. The plugin is free under Apache-2.0. It reads your plans and context files often, so it uses more of your plan or API budget.
- Q: Is it an official Google product? A: It lives in the gemini-cli-extensions GitHub organisation, and contributors must sign Google's contributor agreement (CONTRIBUTING.md). The README does not call it an official product, and the Gemini CLI gallery says Google does not vet, endorse or guarantee the extensions it lists.
- Q: Can it undo its own work safely? A: Yes, if you choose Safe.
/conductor:conductor-revertfinds the commits for a track, phase or task, shows you the plan, and then asks you to pick Safe (git revert, new commits that undo the change) or Hard Reset (git reset --hard, which the skill marks destructive because uncommitted changes are lost). - Q: Which version do I have? A: The newest commit on main. Ignore the v0.4.1 release on GitHub; it belongs to the older Gemini CLI extension.
Sources
- github.com/gemini-cli-extensions/conductor
- github.com/gemini-cli-extensions/conductor/tree/6e8f9a860bcdd6a2c423473c12e745200688c633/skills
- github.com/gemini-cli-extensions/conductor/releases
- github.com/gemini-cli-extensions/conductor/pull/171
- geminicli.com/extensions/
- code.claude.com/docs/en/skills