agent operations skill risk: low

Conductor Project Artifacts Validator

Provides shell commands to verify the conductor directory, tracks, and required markdown files, plus usage rules, status marker patterns for tracks.md and plan.md, track ID format,…

SKILL 1 file

SKILL.md

Download

---
name: conductor-validator
description: "Validates Conductor project artifacts for completeness,"
---
# 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
```

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

REQUIRED CONTEXT

conductor directory
track directories
required files (index.md, product.md, tech-stack.md, workflow.md, tracks.md)

ROLES & RULES

Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Do not use this skill when the task is unrelated to check if conductor directory exists

EXPECTED OUTPUT

Format

plain_text

Constraints

clarify goals, constraints, and required inputs first
apply best practices and validate outcomes
provide actionable steps and verification

SUCCESS CRITERIA

Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.

FAILURE MODES

May be used outside its intended scope.
Output may be treated as substitute for validation.

EXAMPLES

Includes examples of status markers in tracks.md, task markers in plan.md, and Track ID pattern.

CAVEATS

Dependencies

Requires resources/implementation-playbook.md if detailed examples needed.

Missing context

Expected output format or report structure
Success/failure criteria for validation
How to handle or report missing files/directories

Ambiguities

Description sentence is truncated after 'completeness,'
'Use this skill when' and 'Do not use this skill when' sections repeat the placeholder phrase 'check if conductor directory exists'
No definition of what 'completeness' means for the artifacts

QUALITY

OVERALL: 0.28
CLARITY: 0.35
SPECIFICITY: 0.25
REUSABILITY: 0.20
COMPLETENESS: 0.30

IMPROVEMENT SUGGESTIONS

Finish the truncated description and replace all placeholder 'check if conductor directory exists' text with the actual intended task scope
Add an explicit 'Output' section specifying the required validation report format
Define concrete completeness rules instead of generic instructions like 'Apply relevant best practices'

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.