Creating, managing, or working with Conductor tracks

Track management

by wshobson · MIT license · ★ 39,857 on GitHub · v1.0.0 · updated Sep 21

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.

---
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

Overview

Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.

Manual install (npx, ZIP)

Claude Codenpx skills add wshobson/agents --skill track-management -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/wshobson/agents/tar.gz/4236bb91f839 \
  | tar -xz -C ~/.claude/skills --strip-components=4 agents-4236bb91f839/plugins/conductor/skills/track-management

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/f7b4c8f01e9529c7012b/track-management.zip" -OutFile "$env:TEMP\track-management.zip"; Expand-Archive "$env:TEMP\track-management.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md1.6 KB
references/1 file · 12.1 KB

Read the files here

wshobson/4236bb92 files

SKILL.md1.6 KB

SKILL.md

Show the full text37 lines

track-management/SKILL.md37 lines · 1.6 KB

PreviewCode

Outline

RawView on GitHub

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

One track, one concern: Keep tracks focused on a single logical change
Small phases: Break work into phases of 3-5 tasks maximum
Verification after phases: Always include verification tasks
Update markers immediately: Mark task status as you work
Record SHAs: Always note commit SHAs for completed tasks
Review specs before planning: Ensure spec is complete before creating plan
Link dependencies: Explicitly note track dependencies
Archive, don't delete: Preserve completed tracks for reference
Size appropriately: Keep tracks between 1-5 days of work
Clear acceptance criteria: Every requirement must be testable

1	---
2	name: track-management
3	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.
4	version: 1.0.0
5	---
6
7	# Track Management
8
9	Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.
10
11	## When to Use This Skill
12
13	- Creating new feature, bug, or refactor tracks
14	- Writing or reviewing spec.md files
15	- Creating or updating plan.md files
16	- Managing track lifecycle from creation to completion
17	- Understanding track status markers and conventions
18	- Working with the tracks.md registry
19	- Interpreting or updating track metadata
20
21	## Detailed patterns and worked examples
22
23	Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
24
25	## Best Practices
26
27	1. One track, one concern: Keep tracks focused on a single logical change
28	2. Small phases: Break work into phases of 3-5 tasks maximum
29	3. Verification after phases: Always include verification tasks
30	4. Update markers immediately: Mark task status as you work
31	5. Record SHAs: Always note commit SHAs for completed tasks
32	6. Review specs before planning: Ensure spec is complete before creating plan
33	7. Link dependencies: Explicitly note track dependencies
34	8. Archive, don't delete: Preserve completed tracks for reference
35	9. Size appropriately: Keep tracks between 1-5 days of work
36	10. Clear acceptance criteria: Every requirement must be testable
37