fix(conductor): align file formats with Claude Code plugin conventions

- Remove YAML frontmatter from command files (commands don't use frontmatter)
- Remove non-standard fields (color, tools) from conductor-validator agent
- Simplify agent description to single line format

plugins/conductor/agents/conductor-validator.md

@@ -1,32 +1,7 @@
 ---
 name: conductor-validator
-description: |
-  Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
-
-  <example>
-  Context: User just ran /conductor:setup
-  User: "Can you verify conductor is set up correctly?"
-  Assistant: Uses conductor-validator agent to check the setup
-  </example>
-
-  <example>
-  Context: User getting errors with conductor commands
-  User: "Why isn't /conductor:new-track working?"
-  Assistant: Uses conductor-validator agent to diagnose the issue
-  </example>
-
-  <example>
-  Context: Before starting implementation
-  User: "Is my project ready for /conductor:implement?"
-  Assistant: Uses conductor-validator agent to verify prerequisites
-  </example>
+description: Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
 model: opus
-color: cyan
-tools:
-  - Read
-  - Glob
-  - Grep
-  - Bash
 ---
 
 You are an expert validator for Conductor project artifacts. Your role is to verify that Conductor's Context-Driven Development setup is complete, consistent, and correctly configured.

plugins/conductor/commands/implement.md

@@ -1,9 +1,4 @@
----
-name: implement
-description: Execute tasks from a track's implementation plan following workflow rules
-model: opus
-argument-hint: "[track-id]"
----
+# Implement Track
 
 Execute tasks from a track's implementation plan, following the workflow rules defined in `conductor/workflow.md`.
 

plugins/conductor/commands/new-track.md

@@ -1,9 +1,4 @@
----
-name: new-track
-description: Create a new feature or bug track with specification and phased implementation plan
-model: opus
-argument-hint: "[track description]"
----
+# New Track
 
 Create a new track (feature, bug fix, chore, or refactor) with a detailed specification and phased implementation plan.
 

plugins/conductor/commands/revert.md

@@ -1,17 +1,4 @@
----
-name: revert
-description: Git-aware undo by logical work unit (track, phase, or task)
-model: opus
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - AskUserQuestion
-argument-hint: "[track-id | track-id:phase | track-id:task]"
----
+# Revert Track
 
 Revert changes by logical work unit with full git awareness. Supports reverting entire tracks, specific phases, or individual tasks.
 

plugins/conductor/commands/setup.md

@@ -1,9 +1,4 @@
----
-name: setup
-description: Initialize project with Conductor artifacts (product definition, tech stack, workflow, style guides)
-model: opus
-argument-hint: "[--resume]"
----
+# Conductor Setup
 
 Initialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.
 

plugins/conductor/commands/status.md

@@ -1,13 +1,4 @@
----
-name: status
-description: Display project progress overview including tracks, phases, and tasks
-model: opus
-allowed-tools:
-  - Read
-  - Glob
-  - Grep
-argument-hint: "[track-id]"
----
+# Conductor Status
 
 Display the current status of the Conductor project, including overall progress, active tracks, and next actions.