track-management

Manage Conductor track lifecycles with standardized IDs and metadata.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/vinothpandian/v-marketplace --skill track-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: track-management
Source: https://github.com/vinothpandian/v-marketplace/tree/main/plugins/claude-conductor/skills/track-management
Command: npx skills add https://github.com/vinothpandian/v-marketplace --skill track-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track management and lifecycle orchestration for Conductor tracks, ensuring consistent structure and traceability across the project.

Core Features & Use Cases

  • Create and manage track lifecycles: from idea to completion with standardized IDs and metadata.
  • Parse and apply plan and spec files to drive execution and progress.
  • Enforce track-related conventions within the repository and tooling.

Quick Start

Create a new track by defining its shortname, track type, and plan, then commit the metadata and add the entry to tracks.md.

Frequently Asked Questions about track-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Conductor track lifecycles from planning to completion?

Track management enforces the folder structure conductor/tracks/<track_id> and the track_id format shortname_YYYYMMDD, preventing duplicate tracks and standardizing lifecycle governance across your project.

How do I create a new Conductor track with the correct ID format and metadata?

Required metadata for a Conductor track includes metadata.json, spec.md, and plan.md files inside the conductor/tracks/<track_id> folder, ensuring standardized planning and lifecycle governance.

What's the best way to prevent duplicate track IDs in a Conductor workflow?

Track management supports parsing plan.md and spec.md files to drive execution and progress, applying their content to update track statuses and maintain lifecycle consistency within the repository.

Can I update Conductor track statuses and parse plans without manual repository edits?

You need a project repository to support Conductor track management, as it enforces the conductor/tracks/<track_id> folder structure and updates the tracks.md file within your existing repository environment.