---
name: gestion-tracks-conductor
description: Guía para crear, gestionar y completar tracks de trabajo en el sistema Conductor, organizando features, bugs y refactors en fases de especificación, planificación e implementación. Incluye convenciones de ciclo de vida, marcadores de estado y registro de tracks.
license: MIT
metadata:
  id: 2612b6c3
  slug: gestion-tracks-conductor
  titulo: "Gestión de Tracks Conductor"
  servicio: Operaciones-PMO
  categoria_recurso: Plantillas-Documentos
  tipo: referencia
  nivel: intermedio
  idioma: es
  idioma_original: en
  acceso: gratis
  precio_eur: 0
  plataformas: [Claude Code, Codex CLI, OpenCode, Cursor, Gemini CLI]
  dependencias: [conductor-plugin, wshobson/agents]
  licencia: { spdx: MIT, redistribuible: true, uso_comercial: true }
  fuente:
    repo: wshobson/agents
    url: https://github.com/wshobson/agents/tree/main/plugins/conductor/skills/track-management
    commit: cc37bfd
    autor: wshobson
    nombre_original: track-management
    duplicados_en: []
  seguridad: { veredicto: seguro, riesgo: bajo, escaneado: "2026-06-14", motor: "grep-estatico+auditor-llm" }
  ficha:
    que_hace: "Gestiona el ciclo de vida completo de unidades de trabajo (tracks) en el framework Conductor, desde la especificación hasta el archivo."
    como_lo_hace: "Proporciona guías y buenas prácticas para crear spec.md y plan.md, actualizar marcadores de estado, registrar SHAs de commits y mantener el registro tracks.md."
  content_hash: "2612b6c3be85fa95c92a356bdb1ff5893a0537ba2eafb1b6681fb37db3d32857"
  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