track-management Skill for Claude: What It Does and How to Install It
Makes Claude manage Conductor tracks: write spec.md and plan.md, update status markers and keep the tracks registry current.
- Installs
- 10.5K
- on skills.sh
- Stars
- 42.1K
- on GitHub
- Files
- 1
- besides SKILL.md
- Updated
- Oct 2026
- last repo commit
This skill is part of wshobson's Conductor plugin. It teaches Claude what a track is: a unit of work (feature, bug, chore or refactor) with a spec.md, a plan.md and metadata, listed in a tracks.md registry.
SKILL.md carries ten best practices, such as small phases of 3-5 tasks and recording commit SHAs. The lifecycle, file formats, status markers and sizing rules are in references/details.md. Creating and reverting tracks use the plugin's commands, /conductor:new-track and /conductor:revert, so install the plugin for the full workflow.
Good for
- Developers using the Conductor plugin for feature, bug and refactor work
- Teams that want specs and phased plans before coding
- Anyone reviewing or updating plan.md status markers
- Maintainers archiving finished tracks
Install track-management
Claude Code
- 1
Copy this prompt.
Install the track-management skill in Claude Code. Run this command: /plugin marketplace add wshobson/agents /plugin install conductor@claude-code-workflows Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Pick one route. The plugin routes install the whole conductor plugin: 1 agent, 6 commands and 3 skills (counted from the plugin folder in the repo tree, which has no hooks or MCP config files). The skills-only routes install just this skill, with no agents or commands. The conductor plugin adds the /conductor commands that the skill refers to.
Built from the package data we hold. Not yet tested by us. Source.
What's in the skill
When it loads
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
Sections in SKILL.md
- When to Use This Skill
- Detailed patterns and worked examples
- Best Practices
Key facts
- Author
- wshobson (repo owner)
- License
- MIT
- Installs on skills.sh
- 10,487 (Nov 2, 2026)
- Last repo commit
- Oct 30, 2026
What it includes
feature, bug, chore and refactor; IDs look like user-auth_20250115
Track types and IDsCreation, implementation and completion, with what to do at each step
Track lifecycleOverview, requirements, acceptance criteria, scope, dependencies, risks, open questions
Write ·
spec.md structurePhases of tasks with verification steps and a checkpoint table
Write ·
plan.md structure[ ] pending, [~] in progress, [x] complete with SHA, [-] skipped, [!] blocked
Write ·
Status markersActive, completed and archived track tables
Write ·
tracks.md registryTrack id, title, type, status, priority and timestamps
Write ·
metadata.json fieldsCreate, start, complete a phase, complete or revert a track
Creating a track uses /conductor:new-track and reverting uses /conductor:revert.
Write ·
Track operationsRight-sized tracks, plus spec and plan quality checklists
Sizing and quality checklistsTen rules, from one concern per track to archiving instead of deleting
Best practices
From the official docs
Permissions
Low risk
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
The plugin agent can run shell commands
Its front matter lists Read, Glob, Grep and Bash. Install only the skill if you do not want the agent. github.com
Revert undoes work
The details file describes /conductor:revert, which lets you revert a track, phase or task and asks you to confirm. Check what it will undo first. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | No read-only mode. Use version control. |
|---|---|
| Sign-in and keys | SKILL.md and details.md do not mention any account or key. |
| Scopes |
|
Questions
How do I install track-management?
Use the install box at the top of this page and start with the conductor plugin route. The skill describes tracks, but /conductor:new-track and the other commands come from the plugin. The skills-only commands install just this skill.
What does the track-management skill do?
It teaches Claude how Conductor tracks work. Claude uses it to write and review spec.md and plan.md, update status markers and keep tracks.md in step.
What is a Conductor track?
A track is a logical work unit for a feature, bug fix, chore or refactor. It goes through a specification, a plan and implementation, and the details file defines each file's format.
Do I need the whole conductor plugin?
For the full workflow, yes. The plugin folder holds 1 agent, 6 commands (implement, manage, new-track, revert, setup, status) and 3 skills, counted from the repo tree, with no hooks or MCP config files. The skill alone gives Claude the file conventions but not the commands.
How big should a track be?
SKILL.md says to keep tracks between 1 and 5 days of work and phases to 3-5 tasks, with verification after each phase.
Is track-management safe to install?
The skill folder holds SKILL.md and one reference file, with no scripts. The plugin route adds the conductor-validator agent, which has Bash among its tools, plus commands that edit track files. Review what Claude changes in your repo.
Does track-management work in Codex, Cursor or the Claude app?
The README documents Claude Code and Codex CLI plugin routes, and skills-only installs for the tools it lists: Cursor, OpenCode, Antigravity CLI, GitHub Copilot and Pi. We left the Claude app upload out of the install box because this skill's commands run in a terminal.
Information
updated Nov 2, 2026
- Repository
- wshobson/agents
- Folder
plugins/conductor/skills/track-management
Sources
Docs, issue trackers and discussions this page is built from.
Show all 3Hide
- track-management SKILL.md · github.com
- track-management references/details.md · github.com
- wshobson/agents README · github.com