Guide · Agent skill
How to use the Track Management agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The track-management skill is a set of instructions that teaches an AI agent how to work with Conductor tracks, the logical work units used to organise features, bugs and refactors. After installing it, you can ask your agent to create a track, write its spec and plan, and keep task status current, and it will follow the conventions the skill describes. This guide covers what the skill does, how to install it, how to trigger it and the safety points to check.
Track Managementwshobson/agents · MIT Download the skill Quick start
- 1Download the ZIP. Download the track-management skill ZIP from the skill's page.
- 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder for one project.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the ZIP.
- 4Check the files. Confirm the folder contains SKILL.md and references/details.md.
- 5Ask for track work. Make a request that names the track, its type and the file you want, such as a spec.md or plan.md.
- 6Review the output. Check the spec, plan and tracks.md changes before committing them.
What the track-management skill makes the agent do
The skill teaches an agent the conventions of Conductor tracks. A track is a work unit that groups a feature, bug, or refactor, and carries a specification, a phased plan, and metadata about status and progress.
With the skill loaded, the agent knows how to write spec.md and plan.md files, keep task status markers and the tracks.md registry up to date, record commit SHAs for completed tasks, and move a track through creation to completion. When the summary guidance is not enough, it can read references/details.md for worked examples.
- Create feature, bug, or refactor tracks
- Write or review spec.md files
- Create or update plan.md files with phases of 3-5 tasks
- Update task status markers as work progresses
- Keep the tracks.md registry current
- Record commit SHAs for completed tasks
Install the track-management skill
You can install the skill in one of three places. For a personal setup, download the ZIP from the skill's page and unzip it into ~/.claude/skills/. To share it with one project, unzip it into that project's .claude/skills/ folder. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.
After installing, the folder should contain SKILL.md and references/details.md.
- Personal: unzip into ~/.claude/skills/
- Project only: unzip into the project's .claude/skills/
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
How to trigger the skill with natural requests
You do not need a special command. The skill's description tells the agent when to use it, so ordinary requests that mention Conductor tracks, spec.md, plan.md, or track lifecycle work will load it. Name the work and the file so the agent knows the context.
Be specific about the track type and the stage you are at. Good requests say what the track is for and what you want from the file.
- "Create a new feature track for CSV export and draft its spec.md."
- "Write a plan.md for the login bug track, split into phases of no more than five tasks."
- "Mark tasks 1.1 and 1.2 as done in the payments refactor track and record their commit SHAs."
- "Add the new track to tracks.md and link it to the auth track as a dependency."
- "Review spec.md for the search track and tell me which requirements are not testable."
Examples of what the agent produces
Track types in the reference file are feature, bug, chore, and refactor. A feature track covers new user-facing functionality or integrations. A bug track covers defect fixes, and a refactor track covers code improvement without behaviour change.
The best practices in the skill ask the agent to keep each track to one concern, size it between 1 and 5 days of work, archive completed tracks rather than delete them, and write testable acceptance criteria. Expect the agent to apply these when it drafts files.
- Refactor track: restructure a module with no behaviour change and verification tasks after each phase
- Bug track: fix an incorrect behaviour and link it to the feature track it affects
- Chore track: update dependencies and document configuration changes
Safety, requirements and limits
The skill lists no required tools or packages. It does not run scripts and does not use the network. It is a set of Markdown instructions, so the main risk is that the agent edits your spec, plan, and tracks.md files, which you should review in version control.
The skill is specific to Conductor's file-based conventions. If your project uses a different process, the agent's output will not match it.
- Runs scripts: no
- Uses network: no
- Requirements: none listed
- Review changes to spec.md, plan.md and tracks.md before committing
What people use it for
- Drafting a spec.md for a new feature track with testable acceptance criteria
- Splitting a refactor into phases of 3-5 tasks, each followed by a verification task
- Updating task status markers and recording commit SHAs after finishing work
- Keeping the tracks.md registry accurate when tracks are added, linked or completed
Frequently asked questions
How do I install the track-management skill?
Download the ZIP from the skill's page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.
What do I need to use the track-management skill?
The skill lists no requirements. It does not run scripts and does not use the network. You do need a project that follows the Conductor workflow, since the guidance is built around its spec.md, plan.md and tracks.md conventions.
Is the track-management skill free?
The skill is published under the MIT licence, as stated on its page. The source does not list pricing for it, so check the licence text on the repository for the terms.
Does the skill work with projects that do not use Conductor?
Not well. The skill is specific to Conductor's tracks and file conventions, so projects using a different process will get guidance that does not match their workflow. Non-technical users looking for general project management help should use a tool built for that purpose.
What is the difference between a feature, bug, chore and refactor track?
A feature track covers new functionality, a bug track covers defect fixes, a chore covers maintenance such as dependency updates, and a refactor covers code improvement without behaviour change. The reference file gives examples for each type.
Why won't the agent use the skill when I ask for help?
The skill loads from its description, so requests should mention Conductor tracks, spec.md, plan.md or track lifecycle work. Check that the folder is in the correct location and that it contains SKILL.md.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if your team already runs the Conductor workflow and wants an agent to write consistent spec and plan files and keep track status current. Pick something else if your project does not use Conductor's spec.md, plan.md and tracks.md conventions, or if you need general project management help.
Download the skill