use-conductor_skill

Overview

This skill scans a project's conductor/ directory to extract direction, workflows, and task planning information. It surfaces product vision, standards, active work tracks, and per-track plans so you can quickly know what to work on next. The output highlights in-progress tasks, next actionable items, and relevant guidelines to follow.

How this skill works

The skill checks for a conductor/ folder at the project root and reads core files such as product.md, product-guidelines.md, tech-stack.md, workflow.md, and tracks.md. For any active tracks it finds, it opens tracks/<name>/plan.md and spec.md to identify task status markers ([ ], [~], [x]) and the next actionable items. It then summarizes vision, standards, workflow rules, and specific tasks to guide immediate work.

When to use it

• On first day working in a repository to get project direction
• Before starting any new task to find the next approved item
• When you need to follow project-specific workflow or TDD rules
• To check which tracks are active and what work is in progress
• To verify style guides and tech stack decisions before implementing changes

Best practices

• Always open product.md first to understand the goal before modifying code
• Respect the plan order in tracks/*/plan.md and update task markers when you start/finish work
• Follow workflow.md (for example TDD or commit guidelines) and the language style guides in code_styleguides/
• Keep spec.md visible to ensure changes stay in-scope and meet success criteria
• When updating plan.md include brief notes or commit SHAs for completed tasks

Example use cases

• User asks “What should I work on next?” — skill finds active track and returns the next [ ] task from plan.md
• Onboarding a new contributor — summarize product vision, guidelines, and where active work lives
• Preparing a PR — confirm relevant style guide, tech decisions, and the track spec to ensure alignment
• Daily standup prep — list [~] in-progress tasks and outstanding [ ] items across tracks