conductor-revert

name	conductor-revert
description	Reverts logical units of work (Tracks, Phases, or Tasks) by analyzing git history and synchronizing the Conductor plans. Use when a user wants to undo specific changes and ensure the project's documentation reflects the rolled-back state.
metadata	{"version":"0.4.1"}

Conductor Revert

Overview

This skill is a Git-aware assistant. Unlike a standard git revert, it understands the relationship between implementation commits and the Conductor documentation. It ensures that when code is reverted, the corresponding plan.md and tracks.md files are also reset to their previous states.

It is designed to handle common non-linear Git histories, such as rewritten commits (from rebase/squash) and merge commits, with robust "Ghost" commit detection and plan-update commit association.

When to Use

• When a user says "Undo that task," "Revert the last phase," or "I want to delete this track and its changes."
• To cleanly roll back a feature that isn't working as expected.

Workflow

The revert process follows 4 phases:

Phase 1: Interactive Target Selection & Confirmation

Two interaction paths:

• Path A (Direct Confirmation): When the user provides a specific target (e.g., track ID). Confirm the selection and proceed.
• Path B (Guided Selection Menu): When no target is provided. Scan all plans for in-progress items (top 3), or fallback to the 3 most recently completed items. Present a unified hierarchical menu with a max of 4 choices plus an automatically-added "Other" option.

Phase 2: Git Reconciliation & Verification