Skip to main content
skill Claude Code CX Codex Cursor

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.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add wshobson/agents
/plugin install conductor@claude-code-workflows
Open on GitHub

What 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.md before 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-workflows

This installs the whole conductor plugin with all its skills

2Skills CLI (Vercel)

npx skills add wshobson/agents --skill track-management -a claude-code

3Manually: put the files in place

~/.claude/skills/track-management/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/track-management/

From the same set213

The whole set →
typescript-advanced-types Seth Hobson Guides an agent through advanced TypeScript types, from generics to conditional and mapped types. Use it for typed libraries, API clients, or strict configuration objects. Claude Code CX Codex Cursor 92,169installs tailwind-design-system Seth Hobson Helps build design systems with Tailwind CSS v4, from theme tokens to component variants. Use it when a project needs shared UI patterns. Claude Code CX Codex Cursor 70,180installs brand-landingpage Travis D. Elliott This skill interviews you about the product and its visual direction, then builds a landing page through Stitch. Use it when there’s no established design yet. Claude Code CX Codex Cursor 39,476installs python-testing-patterns Seth Hobson This skill guides Python testing with pytest, fixtures and mocks. Use it when building a test suite or tracking down failing checks. Claude Code CX Codex Cursor 36,943installs python-performance-optimization Seth Hobson This skill profiles Python code to locate CPU and memory bottlenecks. Use it when an application responds slowly or consumes too many resources. Claude Code CX Codex Cursor 35,675installs nextjs-app-router-patterns Seth Hobson This skill covers Next.js App Router patterns for rendering, routing, and data fetching. Use it when starting an App Router project or moving from Pages Router. Claude Code CX Codex Cursor 32,529installs api-design-principles Seth Hobson Use this skill to plan or review REST and GraphQL APIs. It helps when writing a specification or setting API conventions for a team. Claude Code CX Codex Cursor 30,348installs code-review-excellence Seth Hobson This skill guides pull request reviews, catches logic and security issues, and helps teams give specific feedback. Use it for review standards or developer mentoring. Claude Code CX Codex Cursor 30,193installs

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

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor