Skill

conductor-manage

Manages Conductor track lifecycle: archive, restore, delete, rename, list status, and cleanup orphaned artifacts. Useful for handling active, completed, and archived tracks in repositories.

developer-tools

git-workflow

Install

npx claudepluginhub joshuarweaver/cascade-code-general-misc-2 --plugin rmyndharis-antigravity-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Manage the complete track lifecycle including archiving, restoring, deleting, renaming, and cleaning up orphaned artifacts.

Supporting Assets

resources/implementation-playbook.md

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Stars682

Forks124

Last CommitJan 18, 2026

Actions

View Source View Plugin View on GitHub View README

Track Manager

Manage the complete track lifecycle including archiving, restoring, deleting, renaming, and cleaning up orphaned artifacts.

Use this skill when

Archiving, restoring, renaming, or deleting Conductor tracks
Listing track status or cleaning orphaned artifacts
Managing the track lifecycle across active, completed, and archived states

Do not use this skill when

Conductor is not initialized in the repository
You lack permission to modify track metadata or files
The task is unrelated to Conductor track management

Instructions

Verify conductor/ structure and required files before proceeding.
Determine the operation mode from arguments or interactive prompts.
Confirm destructive actions (delete/cleanup) before applying.
Update tracks.md and metadata consistently.
If detailed steps are required, open resources/implementation-playbook.md.

Safety

Backup track data before delete operations.
Avoid removing archived tracks without explicit approval.

Resources

resources/implementation-playbook.md for detailed modes, prompts, and workflows.