Validate Conductor Directory Structure

This skill checks whether a project's conductor/ directory structure is present and correctly organized: confirming the conductor/ directory and its conductor/tracks/ subdirectory exist, and verifying the presence of the required files index.md, product.md, tech-stack.md, workflow.md, and tracks.md. It also documents the Conductor convention's pattern-matching rules: status markers [ ]/[~]/[x] (not started / in progress / complete) used in both tracks.md for tracks and plan.md for individual tasks, and a track ID naming pattern of <type>_<name>_<YYYYMMDD> (for example feature_user_auth_20250115).

Use it when checking whether a Conductor-managed project's directory and file structure is set up correctly, or when interpreting status markers and track IDs within an existing Conductor project. It is not applicable outside the Conductor convention - a project using a different tracking format or tool falls outside its scope.

The checks are plain shell listing commands:

ls -la conductor/
ls -la conductor/tracks/
ls conductor/index.md conductor/product.md conductor/tech-stack.md conductor/workflow.md conductor/tracks.md

Output is simply whether the directory and each required file exist, plus interpretation of any status markers or track IDs found in tracks.md or plan.md against the documented patterns. For deeper implementation guidance beyond structural validation, the skill points to resources/implementation-playbook.md.

Anyone maintaining or auditing a Conductor-managed project who needs to confirm its structure is intact and correctly interpret its status-marker and track-ID conventions before acting on the project's state.