Conductor Bundle of 3 skills
- Use it when:
- You want an agent to build features from written project context and an agreed plan, across many sessions, approving each phase before it moves on.
- It does:
- Keeps project context files, turns each feature, bug, chore or refactor into a track, a unit of work with a spec and phased plan, then builds it test-first.
- You get:
- A conductor/ folder of product, tech-stack and workflow files and a tracks.md registry; per track, a spec.md, a plan.md marked with task status and commit SHAs, and metadata.
- Pauses:
- At the end of each phase, until you approve its verification checklist.
- Commands:
- setup, new-track and revert steps call /conductor commands that come with the plugin, not the skills; the skills alone include templates and manual steps.
- Based on:
- Google's Conductor extension for Gemini CLI, adapted for Claude Code.
TL;DR
Three skills behind Conductor, a wshobson/agents plugin, one per stage of its cycle: context, then spec and plan, then implementation. context-driven-development keeps a conductor/ folder of Markdown files the agent reads before each piece of work: product.md for what's built and why, product-guidelines.md for voice and terminology, tech-stack.md, workflow.md for rules such as TDD, commit conventions and coverage targets, and tracks.md, the registry of tracks. It gives starter templates, when to update each file and a checklist to run before starting a track. track-management turns a feature, bug, chore or refactor into a track: a folder with spec.md (requirements, testable acceptance criteria, scope, dependencies, risks), plan.md (phases of tasks, each ending in verification) and metadata.json. workflow-patterns then works through the plan one task at a time: mark it in progress, write failing tests, make them pass, refactor, reach 80% coverage, commit, attach a git note and record the SHA in plan.md. At the end of each phase it runs the full test suite, lists manual checks and waits for your approval before a checkpoint commit. Setting up, creating tracks and reverting call /conductor commands, which come with the plugin, not with the skills.
Summarizes the repo at 4bde316.
Any agent, with the skills CLI; the skills only, without the plugin's /conductor: commands
npx skills add wshobson/agents --skill context-driven-development --skill track-management --skill workflow-patterns Claude Code plugin, after /plugin marketplace add wshobson/agents; the skills plus the /conductor: commands
/plugin install conductor@claude-code-workflows Codex plugin; the skills only, without the /conductor: commands
codex plugin marketplace add wshobson/agents && codex plugin add conductor@claude-code-workflows Source on GitHubAll skills from wshobson/agents
- Total Downloads
- 11,500 of context-driven-development, its most installed skill, on skills.sh, Nov 9, 2026
- Repo stars
- 42,334 wshobson/agents
- First seen
- Jan 20, 2026 on skills.sh, its first skill
Its skills, in the order they're used
The ones marked “Only in the bundle” need the rest of it. The others also work alone.
-
context-driven-development
11.5K total downloadsCreates and maintains product, tech-stack, workflow and track documents in a conductor/ folder that the agent reads before each piece of work.
-
track-management
10.6K total downloadsOrganizes work into Conductor tracks: a spec.md and phased plan.md per feature, bug, chore or refactor, tracked with status markers and commit SHAs.
-
Drives a disciplined TDD implementation loop — red-green-refactor, coverage gates, focused commits and git notes, phase checkpoints that wait for approval.
Works task by task through a track's plan.md, in the format track-management defines, updating its status markers and recording each commit's SHA there.