# Track Management

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

Source: https://skillsagentes.com/skills/wshobson/agents/track-management
Repository: https://github.com/wshobson/agents
Author: wshobson
License: MIT
Updated: hace 2 meses
Context cost: 48 tok installed, 420 tok once triggered, 3.5k tok with every bundled file
Bundle: 2 files, 14 KB
Permissions requested: none declared

## Install

```bash
npx -y skills add wshobson/agents --skill track-management --agent claude-code
```

## What it does

- Guía la creación y gestión de tracks de Conductor: unidades de trabajo para features, bugs y refactors
- Estructura el ciclo de vida de un track: spec.md, plan.md y fases de implementación
- Define convenciones de marcadores de estado y metadatos de track
- Mantiene el registro tracks.md actualizado

## Use it when

- Crear nuevos tracks de feature, bug o refactor
- Escribir o revisar archivos spec.md
- Crear o actualizar archivos plan.md
- Gestionar el ciclo de vida del track o interpretar/actualizar su metadata

## What triggers it

- "Crea un nuevo track para esta feature con su spec.md"
- "Ayúdame a escribir el plan.md de este track"
- "Revisa el estado y los marcadores de este track en tracks.md"

## Before you install

- Requiere el sistema de referencias en references/details.md para patrones detallados.

## Files

- SKILL.md — 2 KB
- references/details.md — 12 KB

## SKILL.md

Reproduced verbatim from wshobson/agents under MIT. This section is the upstream document and is in English.

# 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

---

Skills Agentes — https://skillsagentes.com/skills/wshobson/agents/track-management