conductor — Claude Code plugin: context, specs, plans
Turns Claude into a project management tool: context and spec first, code after. Useful when features should follow a plan instead of being improvised.
/plugin marketplace add wshobson/agents
/plugin install conductor@claude-code-workflowsWhat conductor does
The plugin enforces one order of work: context → spec and plan → implement. /conductor:setup creates a conductor/ folder with product.md, tech-stack.md, workflow.md and style guides for the languages you pick. Then /conductor:new-track opens a track for a feature or bug: interactive questions, a spec.md with requirements and a plan.md broken into phases.
Implementation runs through /conductor:implement on a TDD red-green-refactor cycle, updating task markers and stopping at manual verification checkpoints. /conductor:status shows the current phase, completion and blockers. /conductor:revert undoes work by logical unit — track, phase or task — finds the matching commits in git and asks for confirmation first. A separate /conductor:manage command handles the track lifecycle: archive, restore, rename, delete, cleanup.
Setup state lives in setup_state.json, so an interrupted initialization can be resumed in another session. Both new and existing projects are supported. One thing to plan for: everything is stored as files in the repo, so the conductor/ tree has to be committed with the code, or the project context won't travel between machines.
What it helps with
- pin down product vision and tech stack before writing code
- break a feature into phases and tasks with status markers
- run implementation as TDD with manual checkpoints
- revert a whole track instead of hunting individual commits
- archive finished tracks and clean up stale artifacts
Example prompts for the agent
- run /conductor:setup and walk me through the product and stack questions
- create a track for the new feature with /conductor:new-track
- show project progress with /conductor:status
How to install conductor
Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install conductor@claude-code-workflowsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about conductor
How do I install conductor in Claude?
Add the marketplace first: /plugin marketplace add wshobson/agents, then install the plugin: /plugin install conductor@claude-code-workflows.
What does conductor do?
It drives a project through context → spec and plan → implement. It generates product, tech stack and style documents, opens tracks with spec.md and plan.md, executes the plan TDD-style and can revert work by track, phase or task.
What has to happen before the first track?
Run /conductor:setup. It detects whether the project is new or existing, asks about the product and stack, and generates the style guides that later tracks rely on.
Source text
conductor · Apache-2.0
# Conductor - Context-Driven Development Plugin for Claude Code
Conductor transforms Claude Code into a project management tool by implementing **Context-Driven Development**. It enforces a structured workflow: **Context → Spec & Plan → Implement**.
## Philosophy
By treating context as a managed artifact alongside code, teams establish a persistent, project-aware foundation for all AI interactions. The system maintains:
- **Product vision** as living documentation
- **Technical decisions** as structured artifacts
- **Work units (tracks)** with specifications and phased plans
- **TDD workflow** with verification checkpoints
## Features
- **Specification & Planning**: Generate detailed specs and actionable task plans before implementation
- **Context Management**: Maintain style guides, tech stack preferences, and product goals
- **Safe Iteration**: Review plans before code generation, keeping humans in control
- **Team Collaboration**: Project-level context documents become shared foundations
- **Project Intelligence**: Handles both greenfield (new) and brownfield (existing) projects
- **Semantic Reversion**: Git-aware revert by logical work units (tracks, phases, tasks)
- **State Persistence**: Resume setup across multiple sessions
## Commands
| Command | Description |
| ---------------------- | ---------------------------------------------------------------------------------- |
| `/conductor:setup` | Initialize project with product definition, tech stack, workflow, and style guides |
| `/conductor:new-track` | Create a feature or bug track with spec.md and plan.md |
| `/conductor:implement` | Execute tasks from the plan following workflow rules |
| `/conductor:status` | Display project progress overview |
| `/conductor:revert` | Git-aware undo by track, phase, or task |
| `/conductor:manage` | Manage track lifecycle: archive, restore, delete, rename, and cleanup |
## Generated Artifacts
```
conductor/
├── index.md # Navigation hub
├── product.md # Product vision & goals
├── product-guidelines.md # Standards & messaging
├── tech-stack.md # Technology preferences
├── workflow.md # Development practices (TDD, commits)
├── tracks.md # Master track registry
├── setup_state.json # Resumable setup state
├── code_styleguides/ # Language-specific conventions
└── tracks/
├── _archive/ # Archived tracks
└── <track-id>/
├── spec.md # Requirements specification
├── plan.md # Phased task breakdown
├── metadata.json # Track metadata
└── index.md # Track navigation
```
## Workflow
### 1. Setup (`/conductor:setup`)
Interactive initialization that creates foundational project documentation:
- Detects greenfield vs brownfield projects
- Asks sequential questions about product, tech stack, workflow preferences
- Generates style guides for selected languages
- Creates tracks registry
### 2. Create Track (`/conductor:new-track`)
Start a new feature or bug fix:
- Interactive Q&A to gather requirements
- Generates detailed specification (spec.md)
- Creates phased implementation plan (plan.md)
- Registers track in tracks.md
### 3. Implement (`/conductor:implement`)
Execute the plan systematically:
- Follows TDD red-green-refactor cycle
- Updates task status markers
- Includes manual verification checkpoints
- Synchronizes documentation on completion
### 4. Monitor (`/conductor:status`)
View project progress:
- Current phase and task
- Completion percentage
- Identified blockers
### 5. Revert (`/conductor:revert`)
Undo work by logical unit:
- Select track, phase, or task to revert
- Git-aware: finds all associated commits
- Requires confirmation before execution
### 6. Manage (`/conductor:manage`)
Manage track lifecycle:
- Archive completed tracks with reason tracking
- Restore archived tracks to active state
- Delete tracks permanently (with safeguards)
- Rename track IDs with reference updates
- Cleanup orphaned artifacts and stale tracks
## Installation
```bash
/plugin install conductor
```
## Acknowledgments
This plugin is based on [Conductor](https://github.com/gemini-cli-extensions/conductor) by Google, originally developed for Gemini CLI.
Adapted for Claude Code by [@wshobson](https://github.com/wshobson).
## License
Apache License 2.0 - See the [original project](https://github.com/gemini-cli-extensions/conductor) for license details.
© Seth Hobson · Apache-2.0 · wshobson/agents