Conductor plugin
A Google plugin for spec-driven development: project context, a spec and a plan before code, then implementation that follows the plan
- 3,775 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The agent writes code and files in the repository following the plan
- The revert command changes git history
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/conductorDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent writes code and files in the repository following the plan
- The revert command changes git history
This is third-party code. Review the repository files before installing.
What it does
Conductor gives the agent a fixed order of work: first describe the product, stack and team rules, then write a spec and plan for each task, and only write code after approval. Context lives in a conductor/ folder in the repository, so the whole team and every later agent session can see it. During implementation the agent checks off items in plan.md. There are commands for status, review against the plan and guidelines, and reverting a task, phase or whole track using git history.
Who it is for. For developers and teams who want the agent to plan work and get it approved before writing code.
Good fit when
- You want a feature built from an approved spec rather than ad hoc
- A team works on the project and needs shared context for the agent
- You need to bring an agent into a large existing codebase
Not a fit when
- A two-line fix where planning takes longer than the work
- A tight token budget: reading context and plans noticeably increases usage
Example request
Start a new track to add a dark mode toggle to the settings pageLimitations
The authors warn about higher token usage on large projects. Revert relies on git, so it works only in a repository with a clean commit history. Antigravity and Claude Code are officially supported; the agent's model usually requires access to foreign provider APIs.
How to disable. In Claude Code run /plugin remove conductor and /plugin marketplace remove gemini-cli-extensions/conductor. In Antigravity: agy plugins uninstall conductor. The conductor/ folder in the project can be deleted by hand.
FAQ
What is a track?
A unit of work: a feature or a bug fix. Each track has its own folder with spec.md, plan.md and metadata.json.
Do I need to memorize the commands?
No, the agent recognizes intent from plain requests, such as starting a new track or showing progress.
Discussion
No questions or reviews yet.
Related
PluginsA plugin with three skills for large development work: project analysis, phased tasks tracked as GitHub Issues, parallel agents and code review
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Codely team skills that run agent work in phases: a plan in a file or GitHub issues, review after each phase and a clean commit
A plugin for Codex and Claude Code that runs a task through a chain of roles from planning to an independent audit
A Claude Code plugin: spec-driven development over a single SPEC.md file, a loop of seven commands with no sub-agents
README in short
The README covers installation in Antigravity (via agy or a symlink) and in Claude Code through the plugin marketplace. The lifecycle consists of project setup, creating a track, implementation, plus status, review and revert. Each command lists the files it creates or updates. A separate section explains how to correct badly executed tasks. Apache 2.0 licensed.