track-management

Track Management - Conductor Track Management Guide

Skill Overview

Track Management is a complete guide for creating, managing, and completing Conductor tracks. It helps developers organize feature work, bug fixes, and refactoring tasks through standardization, planning, and implementation phases.

Use Cases

1. Creating a New Development Track

When you need to start a new feature, fix a bug, or refactor code, use this guide to learn how to correctly create a Conductor track, including defining the track type, setting the initial status, and registering it in tracks.md.

2. Writing and Reviewing Track Documentation

When writing spec.md spec documents or plan.md implementation plans, this guide provides best practices and template references to ensure the track documentation has a complete structure and accurate information.

3. Managing a Track’s Lifecycle

When a track progresses from creation to completion, use this guide to understand status-marking conventions, update track metadata, and ensure the information in the tracks.md registry stays in sync.

Core Functions

Track Creation and Initialization

Provides a standard process for creating feature, bug, and refactor tracks, including selecting the track type, setting the initial status, and updating the registry—ensuring each track has clear responsibility boundaries.

Spec and Plan Documentation

Guides the writing of spec.md specification documents and plan.md implementation plans, covering requirement analysis, technical approach, implementation steps, and acceptance criteria—helping the team align on track goals.

Lifecycle and Status Management

Explains the status flow of a track from creation to completion, including status markers such as TODO, IN PROGRESS, and DONE, and how to maintain accurate track metadata in tracks.md.

Frequently Asked Questions

What is a Conductor Track?

A Conductor Track is a logical unit for organizing development work. It splits features, bug fixes, and refactoring tasks into independent tracks. Each track is managed through spec.md (specification) and plan.md (plan) documents and recorded in the tracks.md registry.

What is the difference between spec.md and plan.md?

spec.md is the track’s specification document. It describes what problem will be solved, why it needs to be done, and what success looks like. plan.md is the implementation plan, describing how to implement it, the specific steps, technical approach, and resource requirements. Together, they complement each other—spec defines the goals, while plan defines the path.

How do I register a new track in tracks.md?

Add a new track entry to tracks.md, including the track name, type (feature/bug/refactor), status, owner, and a brief description. When the track status is updated, update this file as well to ensure the registry reflects the project’s current state.