Smithery is now a part of Arcade.dev! Read more in our announcement here
Get help with Conductor - commands, usage examples, and best practices
plugin: conductor updated: 2026-01-20
Conductor implements Context-Driven Development for Claude Code.
Context as a Managed Artifact: Your project context (goals, tech stack, workflow) is documented and maintained alongside your code. This context guides all development work.
Pre-Implementation Planning: Before coding, create a spec (WHAT) and plan (HOW). This ensures clear direction and traceable progress.
Safe Iteration: Human approval gates at key points. Git-linked commits for traceability. Easy rollback when needed.
Initialize Conductor for your project.
Create a new development track.
Execute tasks from your plan.
View project progress.
Git-aware logical undo.
conductor:setup to create context filesconductor:new-track to create your first trackconductor:implement to start workingconductor:status to see progressconductor:revert if you need to roll backconductor/
├── product.md # Project vision and goals
├── tech-stack.md # Technical preferences
├── workflow.md # Development procedures
├── tracks.md # Index of all tracks
└── tracks/
└── {track_id}/
├── spec.md # Requirements specification
├── plan.md # Hierarchical task plan
└── metadata.json
"Conductor not initialized"
Run conductor:setup to initialize the conductor/ directory.
"Track not found" Check tracks.md for available tracks. Track IDs are case-sensitive.
"Revert failed" Check for uncommitted changes. Commit or stash before reverting.
Use conductor:help anytime for this reference.
For issues, check the project documentation or file an issue.
