track-management — Claude Code skill: install
This skill manages Conductor tracks for features, bugs, and refactors. Use it when work needs a clear spec, plan, status, and completion flow.
/plugin marketplace add wshobson/agents
/plugin install conductor@claude-code-workflowsWhat track-management does
track-management guides work with Conductor tracks, the logical units used to organize features, bugs, and refactors. It covers creating and reviewing spec.md, writing plan.md, maintaining the tracks.md registry, and moving tracks through their lifecycle.
The skill sets rules for focused tracks, small phases, verification tasks, acceptance criteria, dependencies, and archiving. It also asks the agent to update task markers as work progresses and record commit SHAs for completed tasks. More detailed patterns live in references/details.md.
Install it when your project uses Conductor and you want consistent track records. Skip it for one-off changes that do not use tracks.
What it helps with
- create a track for a feature, bug, or refactor
- review
spec.mdbefore making a plan - split work into phases and tasks in
plan.md - update task markers and record a commit SHA
- link dependencies and archive a completed track
Example prompts for the agent
- Create a Conductor track for this refactor and draft `spec.md`.
- Review `plan.md`, add verification tasks, and update the task markers.
- Check `tracks.md` and link this track to its dependencies.
How to install track-management
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install conductor@claude-code-workflowsThis installs the whole conductor plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill track-management -a claude-code3Manually: put the files in place
~/.claude/skills/track-management/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/track-management/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill track-management -a codex2Manually: put the files in place
.agents/skills/track-management/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill track-management -a cursor2Manually: put the files in place
.cursor/skills/track-management/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents track-management2Manually: put the files in place
.github/skills/track-management/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/conductor/skills/track-managementManually: put the files in place
.devin/skills/track-management/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set213
The whole set →Similar
Questions about track-management
How do I install track-management in Claude Code?
Run npx skills add wshobson/agents --skill track-management -a claude-code. The skill file is placed at ~/.claude/skills/track-management/SKILL.md.
What does track-management do?
It guides the creation, planning, and completion of Conductor tracks for features, bugs, and refactors. It also covers spec.md, plan.md, tracks.md, and task status markers.
Which files does track-management work with?
The main files are spec.md, plan.md, and tracks.md. Additional patterns and examples are in references/details.md.
Source text
SKILL.md · Apache-2.0
--- name: track-management description: 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. version: 1.0.0 --- # Track Management Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases. ## When to Use This Skill - Creating new feature, bug, or refactor tracks - Writing or reviewing spec.md files - Creating or updating plan.md files - Managing track lifecycle from creation to completion - Understanding track status markers and conventions - Working with the tracks.md registry - Interpreting or updating track metadata ## Detailed patterns and worked examples Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. ## Best Practices 1. **One track, one concern**: Keep tracks focused on a single logical change 2. **Small phases**: Break work into phases of 3-5 tasks maximum 3. **Verification after phases**: Always include verification tasks 4. **Update markers immediately**: Mark task status as you work 5. **Record SHAs**: Always note commit SHAs for completed tasks 6. **Review specs before planning**: Ensure spec is complete before creating plan 7. **Link dependencies**: Explicitly note track dependencies 8. **Archive, don't delete**: Preserve completed tracks for reference 9. **Size appropriately**: Keep tracks between 1-5 days of work 10. **Clear acceptance criteria**: Every requirement must be testable
© Seth Hobson · Apache-2.0 · wshobson/agents