conductor

Conductor Plugin for Claude Code

This is a direct port of Original Gemini Extension

Measure twice, code once.

Conductor is a Claude Code plugin that enables Context-Driven Development. It turns Claude Code into a proactive project manager that follows a strict protocol to specify, plan, and implement software features and bug fixes.

Instead of just writing code, Conductor ensures a consistent, high-quality lifecycle for every task: Context -> Spec & Plan -> Implement.

The philosophy behind Conductor is simple: control your code. By treating context as a managed artifact alongside your code, you transform your repository into a single source of truth that drives every agent interaction with deep, persistent project awareness.

Features

Plan before you build: Create specs and plans that guide the agent for new and existing codebases.
Maintain context: Ensure AI follows style guides, tech stack choices, and product goals.
Iterate safely: Review plans before code is written, keeping you firmly in the loop.
Work as a team: Set project-level context for your product, tech stack, and workflow preferences that become a shared foundation for your team.
Build on existing projects: Intelligent initialization for both new (Greenfield) and existing (Brownfield) projects.
Smart revert: A git-aware revert command that understands logical units of work (tracks, phases, tasks) rather than just commit hashes.

Installation

Prerequisites

Claude Code CLI installed (latest version recommended)
Git (optional, but recommended for revert feature)
Internet connection (for GitHub installation)

Marketplace Setup

This plugin can be distributed via the Claude Code Plugin Marketplace system. The marketplace configuration is defined in .claude-plugin/marketplace.json.

For Users: Installing from a Marketplace

claude plugin marketplace add premithk/claude-conductor
claude plugin install conductor --scope user

Verify Installation

After installation, verify the plugin is working:

# Check if commands are available
claude --help | grep conductor

# You should see:
# /conductor:setup
# /conductor:newTrack
# /conductor:implement
# /conductor:status
# /conductor:revert

Usage

Conductor is designed to manage the entire lifecycle of your development tasks.

Note on Token Consumption: Conductor's context-driven approach involves reading and analyzing your project's context, specifications, and plans. This can lead to increased token consumption, especially in larger projects or during extensive planning and implementation phases.

1. Set Up the Project (Run Once)

When you run /conductor:setup, Conductor helps you define the core components of your project context. This context is then used for building new components or features by you or anyone on your team.

Product: Define project context (e.g. users, product goals, high-level features).
Product guidelines: Define standards (e.g. prose style, brand messaging, visual identity).
Tech stack: Configure technical preferences (e.g. language, database, frameworks).
Workflow: Set team preferences (e.g. TDD, commit strategy). Uses workflow.md as a customizable template.

Generated Artifacts:

conductor/product.md
conductor/product-guidelines.md
conductor/tech-stack.md
conductor/workflow.md
conductor/code_styleguides/
conductor/tracks.md

/conductor:setup

2. Start a New Track (Feature or Bug)

When you're ready to take on a new feature or bug fix, run /conductor:newTrack. This initializes a track — a high-level unit of work. Conductor helps you generate two critical artifacts:

Specs: The detailed requirements for the specific job. What are we building and why?
Plan: An actionable to-do list containing phases, tasks, and sub-tasks.

Generated Artifacts:

conductor/tracks/<track_id>/spec.md
conductor/tracks/<track_id>/plan.md
conductor/tracks/<track_id>/metadata.json

/conductor:newTrack
# OR with a description
/conductor:newTrack Add a dark mode toggle to the settings page

3. Implement the Track

Once you approve the plan, run /conductor:implement. Your coding agent then works through the plan.md file, checking off tasks as it completes them.

Updated Artifacts:

conductor/tracks.md (Status updates)
conductor/tracks/<track_id>/plan.md (Status updates)
Project context files (Synchronized on completion)

/conductor:implement

Conductor will: 1. Select the next pending task. 2. Follow the defined workflow (e.g., TDD: Write Test -> Fail -> Implement -> Pass). 3. Update the status in the plan as it progresses. 4. Verify Progress: Guide you through a manual verification step at the end of each phase to ensure everything works as expected.

During implementation, you can also:

Check status: Get a high-level overview of your project's progress.

  /conductor:status

Revert work: Undo a feature or a specific task if needed.

  /conductor:revert

Commands Reference

Troubleshooting

Plugin not found after installation

Problem: Commands don't appear in --help

Solutions: 1. Check plugin installation:

   ls -la ~/.claude/plugins/ | grep conductor

2. Verify plugin.json exists:

   cat ~/.claude/plugins/claude-conductor/.claude-plugin/plugin.json

3. Restart Claude Code or your terminal

Development

Resources

Claude Code Plugins Documentation: Documentation about using plugins in Claude Code
Original Gemini Extension: The original Conductor extension for Gemini CLI

Changelog

0.1.0 (Current)

Updated to use correct tool names (AskUserQuestion)
Added .gitignore for cleaner repositories
Reorganized utility scripts
Enhanced plugin manifest with contributes section
Added CONTRIBUTING.md for developers

0.0.1

Initial port from Gemini CLI extension
Core commands: setup, newTrack, implement, status, revert
Template system for workflows and style guides

Legal

License: Apache License 2.0

Summary

Install to Claude Code