Conductor Validator

1---
2name: conductor-validator
3description: Validates Conductor project artifacts for completeness,
4  consistency, and correctness. Use after setup, when diagnosing issues, or
5  before implementation to verify project context.
6allowed-tools: Read Glob Grep Bash
7metadata:
8  model: opus
9  color: cyan
10---
11 
12# Check if conductor directory exists
13ls -la conductor/
14 
15# Find all track directories
16ls -la conductor/tracks/
17 
18# Check for required files
19ls conductor/index.md conductor/product.md conductor/tech-stack.md conductor/workflow.md conductor/tracks.md
20```
21 
22## Use this skill when
23 
24- Working on check if conductor directory exists tasks or workflows
25- Needing guidance, best practices, or checklists for check if conductor directory exists
26 
27## Do not use this skill when
28 
29- The task is unrelated to check if conductor directory exists
30- You need a different domain or tool outside this scope
31 
32## Instructions
33 
34- Clarify goals, constraints, and required inputs.
35- Apply relevant best practices and validate outcomes.
36- Provide actionable steps and verification.
37- If detailed examples are required, open `resources/implementation-playbook.md`.
38 
39## Pattern Matching
40 
41**Status markers in tracks.md:**
42 
43```
44- [ ] Track Name  # Not started
45- [~] Track Name  # In progress
46- [x] Track Name  # Complete
47```
48 
49**Task markers in plan.md:**
50 
51```
52- [ ] Task description  # Pending
53- [~] Task description  # In progress
54- [x] Task description  # Complete
55```
56 
57**Track ID pattern:**
58 
59```
60<type>_<name>_<YYYYMMDD>
61Example: feature_user_auth_20250115
62```
63