Agent Skills
› NeverSight/learn-skills.dev
› use-conductor
use-conductor
GitHub扫描项目根目录下的conductor文件夹，获取产品愿景、技术栈、工作流及任务规划等上下文信息。用于确定当前进行中的任务、理解项目规范并指导后续开发工作。
Trigger Scenarios
开始新项目工作时
需要查找项目背景或指南时
需要了解工作流程方法时
确定进行中或队列中的任务时
Install
npx skills add NeverSight/learn-skills.dev --skill use-conductor -g -y
SKILL.md
Frontmatter
{
"name": "use-conductor",
"description": "Scan conductor\/ directory for project direction, workflows, and task planning when present"
}
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..."
Version History
- e0220ca Current 2026-07-05 21:30
