conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
Best use case
conductor-validator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
Teams using conductor-validator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/conductor-validator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How conductor-validator Compares
| Feature / Agent | conductor-validator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Pattern Matching **Status markers in tracks.md:** ``` - [ ] Track Name # Not started - [~] Track Name # In progress - [x] Track Name # Complete ``` **Task markers in plan.md:** ``` - [ ] Task description # Pending - [~] Task description # In progress - [x] Task description # Complete ``` **Track ID pattern:** ``` <type>_<name>_<YYYYMMDD> Example: feature_user_auth_20250115 ```
Related Skills
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification.
conductor-status
Display project status, active tracks, and next actions
conductor-setup
Initialize project with Conductor artifacts (product definition, tech stack, workflow, style guides)
conductor-revert
Git-aware undo by logical work unit (track, phase, or task)
conductor-new-track
Create a new track with specification and phased implementation plan
conductor-manage
Manage track lifecycle: archive, restore, delete, rename, and cleanup
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow
firecrawl
Official Firecrawl CLI skill for web scraping, search, crawling, and browser automation. Returns clean LLM-optimized markdown. USE FOR: - Web search and research - Scraping pages, docs, and articles - Site mapping and bulk content extraction - Browser automation for interactive pages Must be pre-installed and authenticated. See rules/install.md for setup, rules/security.md for output handling.
super-search
Search your coding memory. Use when user asks about past work, previous sessions, how something was implemented, what they worked on before, or wants to recall information from earlier sessions.
super-save
Save important project knowledge to memory. Use when user wants to preserve architectural decisions, significant bug fixes, design patterns, or important implementation details for team reference.
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reacti...
web-quality-audit
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".