Conductor Validator

This validates your Conductor project structure by checking for required directories and files like index.md, product.md, tech-stack.md, and the tracks folder. It recognizes status markers in your track and task lists ([ ] for pending, [~] for in progress, [x] for complete) and enforces track ID naming patterns. Run it after initial setup, before starting implementation, or when something feels off with your project context. The checks are straightforward file system operations, so it's fast and safe. Honestly most useful as a sanity check when you're context switching back to a project or debugging why Conductor isn't behaving as expected.

skills.sh installs: 205
GitHub stars: 39.4K
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add sickn33/antigravity-awesome-skills --skill conductor-validator --agent claude-code

Installs into .claude/skills of the current project.

Files

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