← Explore all agents

PLANNING WORKFLOW COMPONENTS / Seth Hobson

Conductor artifact validator

A Conductor review profile checking project context, track metadata and status consistency.

“Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.”

01 / THE REASONING

Why this made the selection.

  • It cross-checks track registry entries against directories, plans and metadata rather than trusting a completion checkbox alone.
  • The validation categories distinguish setup, content, track, cross-artifact consistency and state-file correctness.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • plugins/conductor/agents/conductor-validator.md (pinned complete source retained)
  • LICENSE
  • Repository README and current official host configuration documentation
  • plugins/conductor/README.md
  • plugins/conductor/skills/track-management/SKILL.md

Our findings

  • It cross-checks track registry entries against directories, plans and metadata rather than trusting a completion checkbox alone.
  • The validation categories distinguish setup, content, track, cross-artifact consistency and state-file correctness.

Not established by this review

  • Source review only: no agent was installed or invoked. Task correctness, effective host restrictions and integration behaviour were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Use the role in your project.

Upstream setup instructions ↗
  1. Read the pinned source and its licence, then configure an explicitly bounded host context.
  2. Use with the matching Conductor files and command version; restrict Bash and check requirements against the actual templates.
  3. Supply an existing conductor directory and the setup/track state to validate.

Before you start

  • Conductor project artifacts
  • Matching Conductor workflow/track definitions

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/conductor/agents/conductor-validator.md

    Supports: Workflow, inputs, outputs and stated boundaries

  2. Applicable licence ↗Checked

    https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/LICENSE

    Supports: Redistribution and attribution

  3. https://code.claude.com/docs/en/sub-agents.md

    Supports: Host loading and effective permission boundaries

  4. https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/conductor/README.md

    Supports: Dependency setup and source-review boundary

  5. https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/conductor/skills/track-management/SKILL.md

    Supports: Dependency setup and source-review boundary

Evidence & Ask