46 lines
1.6 KiB
Markdown
46 lines
1.6 KiB
Markdown
---
|
|
name: conductor-manage
|
|
description: "Manage track lifecycle: archive, restore, delete, rename, and cleanup"
|
|
risk: unknown
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
# 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.
|
|
|
|
## Limitations
|
|
- Use this skill only when the task clearly matches the scope described above.
|
|
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
|
|
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
|