implement

Conductor Implement

Implement track: $ARGUMENTS

---

1.0 SETUP CHECK

PROTOCOL: Verify Conductor environment is properly set up.

1. Check Required Files: Verify existence of:

   • conductor/product.md
   • conductor/tech-stack.md
   • conductor/workflow.md

2. Handle Missing Files:

   • If ANY missing: HALT immediately
   • Announce: "Conductor is not set up. Please run /conductor-setup first."
   • Do NOT proceed.

---

2.0 TRACK SELECTION

PROTOCOL: Identify and select the track to be implemented.

1. Check for User Input: Check if track name provided as argument.

2. Parse Tracks File: Read conductor/tracks.md

   • Split by --- separator to identify track sections
   • Extract: status ([ ], [~], [x]), description, folder link
   • CRITICAL: If no track sections found: "The tracks file is empty or malformed." → HALT

3. Select Track:

   If track name provided:

   • Exact, case-insensitive match against descriptions
   • If unique match: Confirm "I found track ''. Is this correct?"
   • If no match or ambiguous: Inform user, suggest next available track

   If no track name provided:

   • Find first track NOT marked [x]
   • Announce: "No track name provided. Selecting next incomplete track: ''"
   • If all complete: "No incomplete tracks found. All tasks completed!" → HALT

4. Check Dependencies:

   • Read conductor/tracks/<track_id>/metadata.json
   • If depends_on array is not empty:
     • For each dependency, check status in conductor/tracks.md
     • If ANY not [x] (completed):

       "⚠️ This track has incomplete dependencies:" [List blocking tracks] "Do you want to proceed anyway?" A) Yes - Proceed despite incomplete dependencies B) No - Implement dependencies first

     • If B: Suggest /conductor-implement <first_dependency>

5. Handle No Selection: If no track selected, inform user and await instructions.