| name | conductor-validator |
| description | Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context. |
| allowed-tools | Read Glob Grep Bash |
| metadata | {"model":"opus","color":"cyan"} |
Check if conductor directory exists
ls -la conductor/
Find all track directories
ls -la conductor/tracks/
Check for required files
ls conductor/index.md conductor/product.md conductor/tech-stack.md conductor/workflow.md conductor/tracks.md
## Use this skill when
- Working on check if conductor directory exists tasks or workflows
- Needing guidance, best practices, or checklists for check if conductor directory exists
## Do not use this skill when
- The task is unrelated to check if conductor directory exists
- You need a different domain or tool outside this scope
## Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
## Pattern Matching
**Status markers in tracks.md:**
**Task markers in plan.md:**
**Track ID pattern:**
Example: feature_user_auth_20250115
