Skip to content
Back to search

conductor

A plugin for AI coding agents (Antigravity, Claude Code) enabling Spec-Driven Development to specify, plan, and implement software features.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/gemini-cli-extensions--conductor/badge.svg)](/listings/gemini-cli-extensions--conductor)

HTML

<a href="/listings/gemini-cli-extensions--conductor"><img src="/api/listings/gemini-cli-extensions--conductor/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Conductor is packaged as a standard agent plugin, compatible across modern AI coding agents. Choose the installation method for your environment below.

1. Antigravity

A. End-User Installation (Recommended)

Install directly from GitHub in a single command:

agy plugins install https://github.com/gemini-cli-extensions/conductor

B. Developer Installation (Live-Sync Global Link)

If you are a developer or contributor who wants to fork the repository, write custom skills, or modify rule configurations, clone the repository locally and link it:

1. Clone the repository:

```bash git clone https://github.com/gemini-cli-extensions/conductor.git cd conductor ```

2. Link globally for Antigravity:

```bash mkdir -p ~/.gemini/config/plugins/ && ln -sfn "$(pwd)" ~/.gemini/config/plugins/conductor ```

*Why this method?* Creating a symlink acts as a live development link. Any edits you make in your local Git branch are instantly loaded in real-time without reinstalling!

C. Workspace-Level Isolation

If you want to isolate Conductor strictly inside a specific Git project:

1. Create the local plugins directory in your target project's root:

```bash mkdir -p .agents/plugins/ ```

2. Link Conductor to your local project:

```bash ln -sfn /absolute/path/to/cloned/conductor .agents/plugins/conductor ```

--------------------------------------------------------------------------------

2. Claude Code

End-User Installation

Register the marketplace repository and install the Conductor plugin directly in your Claude Code session:

/plugin marketplace add gemini-cli-extensions/conductor
/plugin install conductor

--------------------------------------------------------------------------------

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 13 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "conductor",
  3. "owner": {
  4. "name": "Conductor"
  5. },
  6. "plugins": [
  7. {
  8. "name": "conductor",
  9. "source": "./",
  10. "description": "Conductor is a set of modular AI agent skills for Claude Code that enables Spec-Driven Development."
  11. }
  12. ]
  13. }
README.md · README · 322 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Conductor Plugin
  2. **Measure twice, code once.**
  3. Conductor is a plugin for AI coding agents (including Antigravity and Claude
  4. Code) that enables **Spec-Driven Development**. It turns your agent into a
  5. proactive project manager that follows a strict protocol to specify, plan, and
  6. implement software features and bug fixes.
  7. Instead of just writing code, Conductor ensures a consistent, high-quality
  8. lifecycle for every task: **Context -> Spec & Plan -> Implement**.
  9. The philosophy behind Conductor is simple: control your code. By treating
  10. context as a managed artifact alongside your code, you transform your repository
  11. into a single source of truth that drives every agent interaction with deep,
  12. persistent project awareness.
  13. --------------------------------------------------------------------------------
  14. ## 🛠 Installation Guide
  15. Conductor is packaged as a standard agent plugin, compatible across modern AI
  16. coding agents. Choose the installation method for your environment below.
  17. ### 1. Antigravity
  18. #### A. End-User Installation (Recommended)
  19. Install directly from GitHub in a single command:
  20. ```bash
  21. agy plugins install https://github.com/gemini-cli-extensions/conductor
  22. ```
  23. #### B. Developer Installation (Live-Sync Global Link)
  24. If you are a developer or contributor who wants to fork the repository, write
  25. custom skills, or modify rule configurations, clone the repository locally and
  26. link it:
  27. 1. Clone the repository:
  28. ```bash
  29. git clone https://github.com/gemini-cli-extensions/conductor.git
  30. cd conductor
  31. ```
  32. 2. Link globally for Antigravity:
  33. ```bash
  34. mkdir -p ~/.gemini/config/plugins/ && ln -sfn "$(pwd)" ~/.gemini/config/plugins/conductor
  35. ```
  36. *Why this method?* Creating a symlink acts as a live development link. Any edits
  37. you make in your local Git branch are instantly loaded in real-time without
  38. reinstalling!
  39. #### C. Workspace-Level Isolation
  40. If you want to isolate Conductor strictly inside a specific Git project:
  41. 1. Create the local plugins directory in your target project's root:
  42. ```bash
  43. mkdir -p .agents/plugins/
  44. ```
  45. 2. Link Conductor to your local project:
  46. ```bash
  47. ln -sfn /absolute/path/to/cloned/conductor .agents/plugins/conductor
  48. ```
  49. --------------------------------------------------------------------------------
  50. ### 2. Claude Code
  51. #### End-User Installation
  52. Register the marketplace repository and install the Conductor plugin directly in
  53. your Claude Code session:
  54. ```bash
  55. /plugin marketplace add gemini-cli-extensions/conductor
  56. /plugin install conductor
  57. ```
  58. --------------------------------------------------------------------------------
  59. ## 🔄 Uninstallation
  60. To safely remove Conductor from your environment:
  61. * **Antigravity:**
  62. * **CLI Installation:** Run `agy plugins uninstall conductor`
  63. * **Global Link:** Run `rm -f ~/.gemini/config/plugins/conductor`
  64. * **Workspace Link:** Run `rm -f .agents/plugins/conductor`
  65. * **Claude Code:** Run `/plugin remove conductor` and `/plugin marketplace
  66. remove gemini-cli-extensions/conductor`
  67. --------------------------------------------------------------------------------
  68. ## 🚀 Features
  69. - **Plan before you build**: Create specs and plans that guide the agent for
  70. new and existing codebases.
  71. - **Maintain context**: Ensure AI follows style guides, tech stack choices,
  72. and product goals.
  73. - **Iterate safely**: Review plans before code is written, keeping you firmly
  74. in the loop.
  75. - **Work as a team**: Set project-level context for your product, tech stack,
  76. and workflow preferences that become a shared foundation for your team.
  77. - **Build on existing projects**: Intelligent initialization for both new
  78. (Greenfield) and existing (Brownfield) projects.
  79. - **Smart revert**: A git-aware revert command that understands logical units
  80. of work (tracks, phases, tasks) rather than just commit hashes.
  81. --------------------------------------------------------------------------------
  82. ## 🎨 Adaptive User Experience (UX Layer)
  83. Conductor natively adapts its user interface to match the specific visual
  84. capabilities of your active developer environment (IDE chat box, terminal
  85. console, or web editor).
  86. This is powered by the integrated **View Layer UX Adapter**:
  87. * **Interactive GUI Modals:** If your host editor supports visual interactive
  88. dialog elements, Conductor will automatically capture selections, decision
  89. interviews, and track options as native graphical modal dialog windows.
  90. * `rules/`: Custom adapter rules tailored for visual IDE environments
  91. (like Antigravity).
  92. * **Graceful CLI Fallback:** If you are operating in a plain text terminal
  93. console (such as Claude Code), Conductor automatically detects the console
  94. environment and adapts all interactive steps into clean, structured
  95. text-based choice menus with bracketed numbers (e.g., `[1] Option A, [2]
  96. Option B`).
  97. This dynamic, semantic adaptation occurs natively behind the scenes with **zero
  98. configuration required**, ensuring the optimal developer experience regardless
  99. of your chosen workflow environment.
  100. --------------------------------------------------------------------------------
  101. ## 📖 Usage & Lifecycle
  102. Conductor manages the entire lifecycle of your development tasks through
  103. namespace-grouped commands.
  104. > [!NOTE] **Note on Token Consumption:** Conductor's spec-driven approach
  105. > involves reading and analyzing your project's context, specifications, and
  106. > plans. This can lead to increased token consumption, especially in larger
  107. > projects or during extensive planning and implementation phases. You can check
  108. > the token consumption in the current session by running `/stats model` (in
  109. > compatible clients).
  110. ### 1. Set Up the Project (Run Once)
  111. When you run `/conductor:conductor-setup`, Conductor helps you define the core
  112. components of your project context. This context is then used for building new
  113. components or features by you or anyone on your team.
  114. - **Product**: Define project context (e.g. users, product goals, high-level
  115. features).
  116. - **Product guidelines**: Define standards (e.g. prose style, brand messaging,
  117. visual identity).
  118. - **Tech stack**: Configure technical preferences (e.g. language, database,
  119. frameworks).
  120. - **Workflow**: Set team preferences (e.g. TDD, commit strategy). Uses
  121. `workflow.md` as a customizable template.
  122. **Generated Artifacts:**
  123. - `conductor/product.md`
  124. - `conductor/product-guidelines.md`
  125. - `conductor/tech-stack.md`
  126. - `conductor/workflow.md`
  127. - `conductor/code_styleguides/`
  128. - `conductor/tracks.md`
  129. ```bash
  130. /conductor:conductor-setup
  131. ```
  132. ### 2. Start a New Track (Feature or Bug)
  133. When you’re ready to take on a new feature or bug fix, run
  134. `/conductor:conductor-new-track`. This initializes a **track** — a high-level
  135. unit of work. Conductor helps you generate two critical artifacts:
  136. - **Specs**: The detailed requirements for the specific job. What are we
  137. building and why?
  138. - **Plan**: An actionable to-do list containing phases, tasks, and sub-tasks.
  139. **Generated Artifacts:**
  140. - `conductor/tracks/<track_id>/spec.md`
  141. - `conductor/tracks/<track_id>/plan.md`
  142. - `conductor/tracks/<track_id>/metadata.json`
  143. ```bash
  144. /conductor:conductor-new-track
  145. # OR with a description
  146. /conductor:conductor-new-track "Add a dark mode toggle to the settings page"
  147. ```
  148. ### 3. Implement the Track
  149. Once you approve the plan, run `/conductor:conductor-implement`. Your coding
  150. agent then works through the `plan.md` file, checking off tasks as it completes
  151. them.
  152. **Updated Artifacts:**
  153. - `conductor/tracks.md` (Status updates)
  154. - `conductor/tracks/<track_id>/plan.md` (Status updates)
  155. - Project context files (Synchronized on completion)
  156. ```bash
  157. /conductor:conductor-implement
  158. ```
  159. During implementation, you can also monitor, revert, or review work using the
  160. following commands:
  161. * **Check status**: Get a high-level overview of your project's progress.
  162. ```bash
  163. /conductor:conductor-status
  164. ```
  165. * **Revert work**: Safely undo a feature, phase, or a specific task.
  166. ```bash
  167. /conductor:conductor-revert
  168. ```
  169. * **Review work**: Review completed work against guidelines and the plan.
  170. ```bash
  171. /conductor:conductor-review
  172. ```
  173. --------------------------------------------------------------------------------
  174. ## 📋 Commands Reference
  175. Command | Description | Generated Artifacts
  176. :------------------------------- | :-------------------------------------------------------------------------------------- | :------------------
  177. `/conductor:conductor-setup` | Scaffolds the project and sets up the Conductor environment. Run this once per project. | `conductor/product.md`<br>`conductor/product-guidelines.md`<br>`conductor/tech-stack.md`<br>`conductor/workflow.md`<br>`conductor/tracks.md`
  178. `/conductor:conductor-new-track` | Starts a new feature or bug track. Generates `spec.md` and `plan.md`. | `conductor/tracks/<id>/spec.md`<br>`conductor/tracks/<id>/plan.md`<br>`conductor/tracks.md`
  179. `/conductor:conductor-implement` | Executes the tasks defined in the current track's plan. | `conductor/tracks.md`<br>`conductor/tracks/<id>/plan.md`
  180. `/conductor:conductor-status` | Displays the current progress of the tracks file and active tracks. | Reads `conductor/tracks.md`
  181. `/conductor:conductor-revert` | Reverts a track, phase, or task by analyzing git history. | Reverts git history
  182. `/conductor:conductor-review` | Reviews completed work against guidelines and the plan. | Reads `plan.md`, `product-guidelines.md`
  183. --------------------------------------------------------------------------------
  184. ## 💡 Best Practices for Task Corrections
  185. When a task or phase in your Conductor project wasn't completed correctly, you
  186. have three native recovery flows:
  187. 1. **Agile In-Flight Corrections**: If you notice an implementation gap while
  188. the agent is actively coding, specify the fix directly in the chat. The
  189. agent will natively adapt its coding loop and verify the fix before
  190. finalizing the task.
  191. 2. **Review Corrections (`/conductor:conductor-review`)**: If issues are caught
  192. after a task/phase is marked completed, run the review command. The review
  193. agent will audit changes, verify style guides, execute tests, and append a
  194. `Review Fixes` tracking phase to `plan.md` to resolve them.
  195. 3. **Safe State Reversions (`/conductor:conductor-revert`)**: If a task
  196. implementation is fundamentally flawed and needs a complete reset, run the
  197. revert command. This rolls back specific Git commits safely and resets the
  198. task state back to pending `[ ]` so you can prompt a fresh approach.
  199. --------------------------------------------------------------------------------
  200. ## 🚂 Getting Started (Natural Language Triggering)
  201. Once Conductor is installed in your environment, you don't need to memorize
  202. slash commands. You can interact with Conductor natively using natural language.
  203. Your active agent will dynamically recognize your intent and execute the
  204. corresponding Conductor protocol in the background:
  205. - **To Scaffold a Project**: > *"Let's create a new Conductor project"* or
  206. *"Run setup for Conductor"*
  207. - **To Plan a Feature**: > *"Let's start a new track to add a login screen"*
  208. or *"Create a plan for the dark mode track"*
  209. - **To Execute the Plan**: > *"Start implementing the active plan"* or
  210. *"Proceed with the implementation"*
  211. - **To Check Progress**: > *"How is our track progress going?"* or *"Show the
  212. current project status"*
  213. - **To Revert or Fix a Task**: > *"Revert the last completed task"* or *"Let's
  214. review the completed phase"*
  215. --------------------------------------------------------------------------------
  216. ## 📂 Repository Structure
  217. - `/skills`: The protocol logic (`SKILL.md`) for each command.
  218. - `/rules`: Platform-specific operational rules files.
  219. --------------------------------------------------------------------------------
  220. ## 🎓 Resources
  221. - [Antigravity Plugins Documentation](https://antigravity.google/docs/plugins):
  222. Official guidelines for using plugins in Antigravity.
  223. - [Claude Code Plugins Documentation](https://code.claude.com/docs/en/discover-plugins):
  224. Guidelines for managing plugins in Claude Code.
  225. - [GitHub Issues](https://github.com/gemini-cli-extensions/conductor/issues):
  226. Report bugs or request features.
  227. - The team gratefully acknowledges Keith Ballinger's original
  228. [.conductor](https://github.com/keithballinger/.conductor) project as the
  229. groundwork for this repository.
  230. --------------------------------------------------------------------------------
  231. ## ⚖ License
  232. - License: [Apache License 2.0](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.