track-management

Track management identifies and organizes software work using track-based units like features, bugs, and refactors to streamline workflows. It governs work progression from conception to completion using standardized track types and lifecycle stages.

To create a new track, use the conductor CLI to initialize it, then draft its spec.md and plan.md files. This begins the track lifecycle, guiding the work unit through creation, implementation, verification, and completion stages.

Track management uses spec.md, plan.md, and tracks.md file formats to define and manage work unit specifications. These markdown files govern track types, standardized IDs, status markers, and metadata throughout the project lifecycle.

Yes, track management provides lifecycle guidance and dependency handling for team collaboration. It supports track types including feature, bug, chore, and refactor, ensuring dependencies are organized across the project lifecycle.

Track management supports four track types: feature, bug, chore, and refactor. Each type uses standardized IDs and status markers to maintain consistent workflows and metadata across the entire project lifecycle.

Use track management when you need to unify scattered software work items into a consistent lifecycle. It is ideal for projects requiring structured spec.md and plan.md workflows with standardized IDs, types, and dependency handling.