Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
Start a fresh conversation. Replace the highlighted placeholders.
Use conductor-validator to review [Conductor project directory] before implementation of [planned change], identifying missing or inconsistent project artifacts and the steps needed to verify readiness.
Required inputs
[Conductor project directory]
[planned change]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: conductor-validatordescription: 'Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context. 'risk: safesource: communitydate_added: '2026-02-27'
Validate Conductor workflow artifacts
When to Use
Inspect a project that actually uses a conductor/ workflow directory after setup, before resuming a track, or when diagnosing inconsistent plans/status. This is distinct from the Rails Conductor desktop-app setup (conductor.json/script/server).
Read-only discovery
# Run from the explicitly selected project root; missing paths are findings, not permission to create them.
ls -ld conductor/ conductor/tracks/
ls conductor/index.md conductor/product.md conductor/tech-stack.md conductor/workflow.md conductor/tracks.md
Validation procedure
Read current project instructions and the actual configured Conductor workflow/version.
Compare the declared artifact list with the project’s real files; report missing, unreadable and extra artifacts separately.
Resolve local index/track links, track IDs and plan/status markers against their referenced content. Do not assume directory presence proves completeness.
Reconcile completed markers with recorded implementation/test evidence and the current revision; report stale or conflicting state without inventing a pass.
Output a concise list of file, observed inconsistency, expected contract and proposed correction. Apply fixes only when requested; preserve existing plans and dirty work.
No implementation-playbook file or runnable validator script is bundled. The procedure above is the complete local guide; optional project-specific automation must actually exist and be reviewed before execution.
Pattern Matching
Status markers in tracks.md:
- [ ] Track Name # Not started
- [~] Track Name # In progress
- [x] Track Name # Complete