conductor-validator

Conductor Validator - Conductor Project Validation Tool

Overview

Conductor Validator is an automated checking tool for validating the integrity, consistency, and correctness of Conductor project artifacts. It is suitable for validating the project context after setup, during issue diagnosis, or before implementation.

Applicable Scenarios

1. Post-Setup Validation

After completing the initial setup of a Conductor project, use this tool to verify that the directory structure, required files, and configurations conform to the specification, ensuring the project’s foundational environment is correct.

2. Issue Diagnosis

When a Conductor project exhibits anomalies or behavior that deviates from expectations, run the validator to quickly identify configuration errors, missing files, or format inconsistencies.

3. Pre-Implementation Validation

Before starting a new feature or making changes, validate the completeness of the project context to avoid developing on an incomplete or misconfigured foundation.

Core Features

1. Directory Structure Validation

Automatically checks whether the Conductor directory exists and verifies the presence of the tracks/ subdirectory and core files (index.md, product.md, tech-stack.md, workflow.md, tracks.md).

2. Pattern Matching Checks

Parses and validates status markers in tracks.md (not started [ ], in progress [~], completed [x]) and task markers in plan.md, ensuring formats comply with conventions.

3. Track ID Format Validation

Checks whether Track IDs follow the <type>_<name>_<YYYYMMDD> format, for example feature_user_auth_20250115, helping maintain a consistent naming convention.

Frequently Asked Questions

When should conductor-validator be run?

It is recommended to run it at three key times: after completing the project initial setup, when diagnosing issues, and before starting new implementations. This helps ensure the project remains in a healthy state.

What specifically does the validator check?

The validator checks whether the Conductor directory exists, whether the tracks subdirectory is complete, whether core files (index.md, product.md, tech-stack.md, workflow.md, tracks.md) are present, and whether status markers and Track ID formats are correct.

What should I do if validation fails?

When validation fails, it will point out the specific location and type of issue. Inspect the report to find missing files or directories, correct nonconforming status markers or Track ID formats, and then re-run the validator until it passes.

What do the status markers in tracks.md represent?

[ ] indicates a track/task not started, [~] indicates in progress, and [x] indicates completed. These markers help the team quickly understand project progress.