Conductor-Beads: Command for Claude Code

Conductor Revert

Revert Conductor work: $ARGUMENTS

Scope: Revert logical units of work tracked by Conductor (Tracks, Phases, Tasks) by investigating Git history and finding all associated commits.

---

1.0 SETUP CHECK

PROTOCOL: Verify project is properly set up before proceeding.

1. Verify Tracks File: Check if conductor/tracks.md exists

   • If NOT exists: HALT and instruct: "The project has not been set up or conductor/tracks.md is corrupted. Please run /conductor-setup or restore the file."

2. Verify Track Content: Check if conductor/tracks.md is not empty

   • If empty: HALT with same message as above

---

2.0 PHASE 1: INTERACTIVE TARGET SELECTION & CONFIRMATION

GOAL: Guide user to clearly identify and confirm the logical unit to revert before analysis begins.

1. Initiate Revert Process: Determine user's target.

2. Check for User-Provided Target:

   • IF target provided (e.g., /conductor-revert track <track_id>): → PATH A: Direct Confirmation
   • IF NO target provided: → PATH B: Guided Selection Menu (default)

3. Interaction Paths:

   PATH A: Direct Confirmation

   1. Find the specific track, phase, or task in tracks.md or relevant plan.md
   2. Ask for confirmation:

      "You asked to revert the [Track/Phase/Task]: '[Description]'. Is this correct?" A) Yes B) No

   3. If "Yes": Establish as target_intent → Proceed to Phase 2
   4. If "No": Ask clarifying questions to find correct item

   PATH B: Guided Selection Menu

   1. Identify Revert Candidates:
      • Scan All Plans: Read conductor/tracks.md AND every conductor/tracks/*/plan.md
      • Prioritize In-Progress: Find ALL Tracks, Phases, Tasks marked [~]
      • Fallback to Completed: If NO in-progress items found, find 5 most recently completed ([x])