use-conductor
16
总安装量
13
周安装量
#21299
全站排名
安装命令
npx skills add https://github.com/89jobrien/steve --skill use-conductor
Agent 安装分布
claude-code
11
codex
10
gemini-cli
10
opencode
9
windsurf
8
Skill 文档
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 metadata
File 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
- Check if
conductor/directory exists at project root - If present, read core files to understand project context:
product.mdfor visionproduct-guidelines.mdfor standardstracks.mdfor active work
- For active tracks (marked
[~]), read the track’splan.mdto find current tasks - 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:
- Respect the plan – Follow the task order in
plan.md - Update status – Mark tasks as
[~]when starting,[x]when done - Follow workflow – Use the TDD methodology if specified
- Maintain standards – Follow
product-guidelines.mdand style guides - Stay in scope – Check
spec.mdfor 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..."