conductor-manage
Manage track lifecycle: archive, restore, delete, rename, and cleanup
Best use case
conductor-manage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Manage track lifecycle: archive, restore, delete, rename, and cleanup
Teams using conductor-manage should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/conductor-manage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How conductor-manage Compares
| Feature / Agent | conductor-manage | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manage track lifecycle: archive, restore, delete, rename, and cleanup
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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.
Related Skills
citation-management
Comprehensive citation management for academic research. Search Google Scholar and PubMed for papers, extract accurate metadata, validate citations, and generate properly formatted BibTeX entries. This skill should be used when you need to find papers, verify citation...
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
conductor-status
Display project status, active tracks, and next actions
conductor-setup
Configure a Rails project to work with Conductor (parallel coding agents)
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow
uv-package-manager
Master the uv package manager for fast Python dependency management, virtual environments, and modern Python project workflows. Use when setting up Python projects, managing dependencies, or optimi...
angular-state-management
Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.
product-manager
Senior PM agent with 6 knowledge domains, 30+ frameworks, 12 templates, and 32 SaaS metrics with formulas. Pure Markdown, zero scripts.
product-manager-toolkit
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritizati...
robius-state-management
CRITICAL: Use for Robius state management patterns. Triggers on: AppState, persistence, theme switch, 状态管理, Scope::with_data, save state, load state, serde, 状态持久化, 主题切换
risk-manager
Monitor portfolio risk, R-multiples, and position limits. Creates hedging strategies, calculates expectancy, and implements stop-losses.
carrier-relationship-management
Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships.