conductor-manage

Conductor Track Manager

Overview

conductor-manage is the track lifecycle management tool for the Conductor framework, supporting a complete set of operations such as archiving, restoring, deleting, renaming tracks, and cleaning up orphaned files.

Use Cases

1. Archiving tracks after project completion

When the project or task corresponding to a Conductor track is completed, you can use --archive to move the track from an active state to an archived state, keeping the workspace tidy while preserving history.

2. Cleaning up orphaned and abandoned files

The --cleanup feature can scan for and remove orphaned files that have no corresponding track metadata (orphaned artifacts), freeing storage space and maintaining repository cleanliness.

3. Track restoration and renaming

Use --restore to reactivate an archived track; or use --rename when renaming a project to update the track name in sync, keeping tracks.md consistent with the actual project structure.

Core Features

Track archiving and restoration

Supports moving active tracks to an archived state (archive), or restoring archived tracks back to active (restore). Operations automatically update tracks.md and related metadata to ensure state consistency.

Track deletion and renaming

Provides a safe track deletion (delete) feature that requires confirmation and recommends backups before execution. The renaming (rename) feature can update the track name and all related references in sync.

Orphaned file cleanup

The cleanup mode scans the conductor/ directory, identifies and removes orphaned files that have no corresponding track records, helping maintain repository cleanliness.

Track status query

Use --list to quickly view the status of all tracks (active, completed, archived), facilitating project management and team collaboration.

Frequently Asked Questions

What operations does conductor-manage support?

It supports six operation modes: --archive (archive), --restore (restore), --delete (delete), --rename (rename), --list (list statuses), and --cleanup (clean up orphaned files).

What data should be backed up before deleting a track?

Before executing --delete, it's recommended to back up the entire conductor/ directory and the tracks.md file. The delete operation is irreversible and will permanently remove all files and metadata related to the track.

How do I clean up orphaned files in Conductor?

Use the command conductor-manage --cleanup to scan for and remove orphaned files that have no corresponding track records. The operation will display a list of files to be deleted before execution, requiring confirmation.

Can archived tracks be restored?

Yes. Use the --restore operation to restore an archived track to active status. After restoration, the track will reappear in the active track list, and all historical data and metadata will be retained.

What permissions does conductor-manage require?

It requires read and write permissions on the conductor/ directory and its subdirectories, as well as permission to modify the tracks.md file. If you're using a version control system, you'll also need the appropriate git commit permissions.