Agent skill

Conductor Track Management

by wshobson in wshobson/agents

“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…”

— description from SKILL.md by wshobson
MITAuto-check passedDevelopment

Install Conductor Track Management

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wshobson/agents track-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/conductor/skills/track-management .claude/skills/track-management && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
track-management
GitHub stars
40k
Used in
9 other repos
Token cost
~420 tokens
SKILL.md length
193 words
Files
2 (incl. references)
Skills in repo
142
Repo updated
First seen
Licence
MIT

At a glance

  • Works in 10 steps: One track, one concern: Keep tracks… → Small phases: Break work into phases of… → Verification after phases: Always… → …
  • SKILL.md covers When to Use This Skill, Detailed patterns and worked… and Best Practices
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

About this skill

“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.”

— description from SKILL.md by wshobson

Conductor Track Management is a skill in wshobson/agents (40k stars). Its SKILL.md is about 420 tokens, with 1 other file in the folder (references), and copies of it appear in 9 other owners' repositories. Licence: MIT.

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit 46891e7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Conductor Track Management loads about 420 tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 193 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~420
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wshobson/agents at commit 46891e7, republished under its MIT licence (© wshobson). 193 words, ~420 tokens.

Download SKILL.mdSave it as .claude/skills/track-management/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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

© wshobson, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/conductor/skills/track-management of wshobson/agents.

  • SKILL.md
  • references/details.md

Open the folder on GitHubat commit 46891e7

Used in 9 other repositories

We found 18 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 9 other GitHub owners. This page covers the copy in wshobson/agents, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Conductor Track Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Conductor Track Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Conductor Track Management this skillwshobson/agents40k9 repos~420Automated safety check: PassMIT
Implementation Plan Writerimbue-ai/bouncer399—~2.1kAutomated safety check: PassAGPL-3.0
Vibe Workflow RouterKhazP/vibe-coding-prompt-template3.1k—~544Automated safety check: NotesMIT
Vertical-Slice Task Plannerowainlewis/blueprint412—~1.5kAutomated safety check: PassMIT
Technical Plan WriterEveryInc/compound-engineering-plugin25k—~1.9kAutomated safety check: PassMIT
Speckit Tasksforyourhealth111-pixel/Vibe-Skills3.6k—~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Turns a feature's goals, requirements and architecture documents into a set of self-contained task files that a developer with no project context can follow.

    399 GitHub stars~2.1k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed
  • Vibe Workflow Router

    KhazP/vibe-coding-prompt-template

    Picks the next useful step for an app project, whether planning a new product, changing an existing app, fixing a bug or writing a handoff, loading only the context needed.

    3.1k GitHub stars~544 tokensUpdated 6 days ago
    Agent WorkflowsAuto-check: notes
  • Vertical-Slice Task Planner

    owainlewis/blueprint

    Breaks a reviewed spec into ordered, vertical-slice tasks that each fit one agent run and one pull request, grouped into milestones when useful.

    412 GitHub stars~1.5k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Technical Plan Writer

    EveryInc/compound-engineering-plugin

    Writes a structured plan for multi-step software or non-software work after research, without writing production code, and pairs with ce-brainstorm and ce-work.

    25k GitHub stars~1.9k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Speckit Tasks

    foryourhealth111-pixel/Vibe-Skills

    Break down implementation plans into actionable task lists. An agent skill from foryourhealth111-pixel/Vibe-Skills.

    3.6k GitHub stars~1.6k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Spec Driven Develop

    zhu1090093659/spec_driven_develop

    Automates pre-development workflow for large-scale complex tasks.

    987 GitHub stars~5.1k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

More from wshobson/agents

All 142 skills in this repo
  • Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.

    40k GitHub starsUsed in 14 repos~1.7k tokens
    Auto-check passed
  • Billing Automation

    wshobson/agents

    Covers building subscription billing: billing cycles, subscription states, invoice generation, proration, tax handling and dunning for failed payments.

    40k GitHub starsUsed in 13 repos~473 tokens
    Auto-check passed
  • Profiles slow Python code with cProfile and memory profilers, then applies targeted fixes for CPU, memory, I/O and query bottlenecks.

    40k GitHub starsUsed in 13 repos~814 tokens
    Auto-check passed
  • Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.

    40k GitHub starsUsed in 12 repos~1.3k tokens
    Auto-check passed
  • Distributed Tracing

    wshobson/agents

    Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks.

    40k GitHub starsUsed in 12 repos~527 tokens
    Auto-check passed
  • Reference for designing and tuning production LLM prompts: few-shot examples, chain-of-thought, structured outputs, templates and system prompts.

    40k GitHub stars~1.3k tokensUpdated 6 days ago
    Auto-check passed

Questions about Conductor Track Management

How do I install Conductor Track Management in Claude Code?

Run `npx skills add wshobson/agents --skill track-management -a claude-code`. Or copy the skill folder (plugins/conductor/skills/track-management in wshobson/agents) into .claude/skills/track-management in your project. Claude Code loads it when a task matches its description.

How do I install Conductor Track Management in Codex?

Run `npx skills add wshobson/agents --skill track-management -a codex`. Or copy the skill folder (plugins/conductor/skills/track-management in wshobson/agents) into .agents/skills/track-management in your project. Codex loads it when a task matches its description.

Can I use Conductor Track Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wshobson/agents --skill track-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/track-management, .gemini/skills/track-management, .github/skills/track-management and .opencode/skills/track-management in your project.

What does Conductor Track Management need to run?

SKILL.md names no scripts, command-line tools or credentials: Conductor Track Management is instructions for the agent only.

Does Conductor Track Management access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Conductor Track Management safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Conductor Track Management use?

Conductor Track Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Conductor Track Management use?

About 420 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.

What are the alternatives to Conductor Track Management?

Skills that share tags, products or a category with Conductor Track Management: Implementation Plan Writer (imbue-ai/bouncer, 399 stars), Vibe Workflow Router (KhazP/vibe-coding-prompt-template, 3.1k stars), Vertical-Slice Task Planner (owainlewis/blueprint, 412 stars) and Technical Plan Writer (EveryInc/compound-engineering-plugin, 25k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Conductor Track Management?

wshobson (a GitHub user) maintains it in wshobson/agents, which has 40,314 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on October 5, 2026.

Source: wshobson/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.