Use Conductor
- 29 installs
- 4 repo stars
- Updated April 11, 2026
- 89jobrien/steve
use-conductor is a Claude Code skill that scans a project's conductor/ directory for direction, workflows, and task planning.
About
use-conductor is a Claude Code skill that scans a project's conductor/ directory for structured project-management files. It reads product vision, guidelines, tech-stack, and per-track plans to understand direction and current tasks. Developers use it to orient an agent to a project's workflow and pick up the next task. It respects the plan, follows the defined methodology, and updates task status markers.
- Scans a conductor/ directory for project direction, workflows, and task planning
- Reads product, guidelines, tech-stack, and track plans to establish context
- Follows and updates task status markers ([ ], [~], [x]) in plan.md files
Use Conductor by the numbers
- 29 all-time installs (skills.sh)
- Ranked #1,873 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
use-conductor capabilities & compatibility
- Capabilities
- project context loading · task tracking
- Use cases
- planning · project management
What use-conductor says it does
Scan the `conductor/` directory at project root for structured project management files that provide direction, workflows,
`[~]` - Task in progress
npx skills add https://github.com/89jobrien/steve --skill use-conductorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 29 |
|---|---|
| repo stars | ★ 4 |
| Last updated | April 11, 2026 |
| Repository | 89jobrien/steve ↗ |
What it does
Scan a conductor/ directory to load project context and workflow, then find and track the next task.
Who is it for?
Developers working in projects that use the conductor/ project-management structure.
Skip if: Projects that do not have a conductor/ directory.
When should I use this skill?
Starting work on a project that may have conductor files, or looking for project context and current tasks.
What you get
The agent oriented to the project's plan, standards, and the next task to work on.
- Loaded project context
- The next in-scope task
- Updated task status markers
By the numbers
- 3 task status markers ([ ], [~], [x])
Files
Use Conductor
Scan the conductor/ directory at project root for structured project management files that provide direction, workflows, and task planning context.
When to Use
Use this skill when:
- Starting work on a project that may have conductor files
- Looking for project context, guidelines, or current tasks
- Needing to understand the project's workflow methodology
- Determining what work is in progress or next in queue
Conductor Directory Structure
The conductor system uses this structure:
conductor/
├── product.md # Product vision and purpose
├── product-guidelines.md # Standards and conventions
├── tech-stack.md # Technology decisions
├── workflow.md # Task execution methodology
├── tracks.md # Index of active work tracks
├── setup_state.json # Setup progress state
├── code_styleguides/ # Language-specific style guides
│ ├── general.md
│ └── python.md
└── tracks/ # Detailed track plans
└── <track_name>/
├── spec.md # Track specification
├── plan.md # Task checklist with progress
└── metadata.json # Track metadataFile Purposes
| File | Purpose |
|---|---|
product.md | Product vision, target audience, core features |
product-guidelines.md | Naming conventions, quality standards, documentation rules |
tech-stack.md | Approved technologies and libraries |
workflow.md | TDD methodology, task workflow, commit guidelines |
tracks.md | High-level index of all work tracks |
tracks/<name>/plan.md | Detailed task checklist with [ ], [~], [x] status |
tracks/<name>/spec.md | Goals, scope, and success criteria for the track |
How to Scan
1. Check if conductor/ directory exists at project root 2. If present, read core files to understand project context:
product.mdfor visionproduct-guidelines.mdfor standardstracks.mdfor active work
3. For active tracks (marked [~]), read the track's plan.md to find current tasks 4. Follow the workflow methodology defined in workflow.md
Task Status Markers
In plan.md files:
[ ]- Task not started[~]- Task in progress[x]- Task completed (may include commit SHA)
Integration with Work
When conductor files are present:
1. Respect the plan - Follow the task order in plan.md 2. Update status - Mark tasks as [~] when starting, [x] when done 3. Follow workflow - Use the TDD methodology if specified 4. Maintain standards - Follow product-guidelines.md and style guides 5. Stay in scope - Check spec.md for what's in/out of scope
Example Usage
Before starting work on a project:
User: "What should I work on next?"
Claude: [Checks for conductor/ directory]
[Reads tracks.md to find active track]
[Reads tracks/<active>/plan.md to find next [ ] task]
"According to the conductor plan, the next task is..."Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What does it read?
Core conductor files like product.md, product-guidelines.md, and tracks.md, plus active track plan.md files.
How are tasks tracked?
Via status markers in plan.md: [ ] not started, [~] in progress, and [x] completed.