conductor-revertlisted

# Revert Track Revert changes by logical work unit with full git awareness. Supports reverting entire tracks, specific phases, or individual tasks. ## Use this skill when - Working on revert track tasks or workflows - Needing guidance, best practices, or checklists for revert track ## Do not use this skill when - The task is unrelated to revert track - You need a different domain or tool outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Pre-flight Checks 1. Verify Conductor is initialized: - Check `conductor/tracks.md` exists - If missing: Display error and suggest running `/conductor:setup` first 2. Verify git repository: - Run `git status` to confirm git repo - Check for uncommitted changes - If uncommitted changes exist: ``` WARNING: Uncommitted changes detected Files with changes: {list of files} Options: 1. Stash changes and continue 2. Commit changes first 3. Cancel revert ``` 3. Verify git is clean enough to revert: - No merge in progress - No rebase in progress - If issues found: Halt and explain resolution steps ## Target Selection ### If argument provided: Parse the argument format: **Full track:** `{trackId}` - Example: `auth_20250115` - Reverts all commits for