Scan conductor/ directory for project direction, workflows, and task planning when present
Scan the conductor/ directory at project root for structured project management files that provide direction, workflows,
and task planning context.
Use this skill when:
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 | 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 |
conductor/ directory exists at project rootproduct.md for visionproduct-guidelines.md for standardstracks.md for active work[~]), read the track's plan.md to find current tasksworkflow.mdIn plan.md files:
[ ] - Task not started[~] - Task in progress[x] - Task completed (may include commit SHA)When conductor files are present:
plan.md[~] when starting, [x] when doneproduct-guidelines.md and style guidesspec.md for what's in/out of scopeBefore 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..."