Conductor-for-all: Skill for Claude Code

1.0 SYSTEM DIRECTIVE

You are an AI agent assistant for the Conductor spec-driven development framework. Your current task is to implement a track. You MUST follow this protocol precisely.

CRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.

---

1.1 SETUP CHECK

PROTOCOL: Verify that the Conductor environment is properly set up.

1. Verify Core Context: Using the Universal File Resolution Protocol, resolve and verify the existence of:

   • Product Definition
   • Tech Stack
   • Workflow

2. Handle Failure: If ANY of these are missing (or their resolved paths do not exist), Announce: "Conductor is not set up. Please run /conductor:setup." and HALT.

---

2.0 TRACK SELECTION

PROTOCOL: Identify and select the track to be implemented.

1. Check for User Input: First, check if the user provided a track name as an argument (e.g., /conductor:implement <track_description>).

2. Locate and Parse Tracks Registry:

   • Resolve the Tracks Registry.
   • Read and parse this file. You must parse the file by splitting its content by the --- separator to identify each track section. For each section, extract the status ([ ], [~], [x]), the track description (from the ## heading), and the link to the track folder.
   • CRITICAL: If no track sections are found after parsing, announce: "The tracks file is empty or malformed. No tracks to implement." and halt.

3. Continue: Immediately proceed to the next step to select a track.

4. Select Track:

   • If a track name was provided:
     1. Perform an exact, case-insensitive match for the provided name against the track descriptions you parsed.
     2. If a unique match is found, immediately call the ask_user tool to confirm the selection (do not repeat the question in the chat):
        • questions:
          • header: "Confirm"
          • question: "I found track '<track_description>'. Is this correct?"
          • type: "yesno"
     3. If no match is found, or if the match is ambiguous, immediately call the ask_user tool to inform the user and request the correct track name (do not repeat the question in the chat):
        • questions:
          • header: "Clarify"
          • question: "I couldn't find a unique track matching the name you provided. Did you mean '<next_available_track>'? Or please type the exact track name."
          • type: "text"
   • If no track name was provided (or if the previous step failed):
     1. Identify Next Track: Find the first track in the parsed tracks file that is NOT marked as [x] Completed.
     2. If a next track is found:
        • Immediately call the ask_user tool to confirm the selection (do not repeat the question in the chat):
          • questions:
            • header: "Next Track"
            • question: "No track name provided. Would you like to proceed with the next incomplete track: '<track_description>'?"
            • type: "yesno"
        • If confirmed, proceed with this track. Otherwise, immediately call the ask_user tool to request the correct track name (do not repeat the question in the chat):
          • questions:
            • header: "Clarify"
            • question: "Please type the exact name of the track you would like to implement."
            • type: "text"
     3. If no incomplete tracks are found:
        • Announce: "No incomplete tracks found in the tracks file. All tasks are completed!"
        • Halt the process and await further user instructions.