track-management

Creates and manages Conductor tracks with spec.md, plan.md, and lifecycle status markers.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill track-management-sanketadlak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: track-management
Source: https://github.com/SanketAdlak/PDMProjectDesign/tree/main/.agents/skills/track-management
Command: npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill track-management-sanketadlak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Organizing features, bugs, and refactors into coherent, trackable work units is difficult without structure. This Skill provides a complete framework for creating Conductor tracks with specifications, phased plans, and lifecycle management so work stays scoped, verifiable, and traceable to commits. ## Core Features & Use Cases - Track Creation: Generate spec.md with functional/non-functional requirements, acceptance criteria, and risk tables, plus plan.md with phased task breakdowns and verification steps. - Lifecycle Management: Manage tracks from creation through implementation to completion using status markers ([ ], [~], [x], [-], [!]), checkpoint SHAs, and the tracks.md registry. - Use Case: When starting a new user authentication feature, use this Skill to create a track with ID user-auth_20250115, generate a specification with acceptance criteria, build a three-phase implementation plan, and track progress with commit-linked task markers. ## Quick Start Create a new Conductor track for the user authentication feature with a specification and phased implementation plan.

Frequently Asked Questions about track-management

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

FAQPage Schema
How do I create a new Conductor track?

Run /conductor:new-track and answer the interactive questions to gather requirements. The workflow generates a spec.md with requirements and acceptance criteria, a plan.md with phased tasks, registers the track in tracks.md, and creates metadata.json.

What is the track ID format in Conductor?

Track IDs follow the pattern {shortname}_{YYYYMMDD}, where shortname is a 2-4 word kebab-case description and the date is the creation date in ISO format. Examples include user-auth_20250115 and fix-login-error_20250115.

What status markers does plan.md support?

Plan.md supports five markers: [ ] for pending, [~] for in progress, [x] for complete with commit SHA, [-] for intentionally skipped, and [!] for blocked tasks. Markers should be updated immediately as work progresses.

How do I handle a blocked track dependency?

Mark blocked tasks with [!] and the blocking reason, update the track status in tracks.md, and document the blocker in metadata.json. If the dependency is substantial, consider creating a separate track to resolve it.

When should a track be split into multiple tracks?

Split a track when it has more than 5 phases, more than 25 tasks, covers multiple unrelated features, or exceeds one week of estimated work. Right-sized tracks complete in 1-5 days with 2-4 phases and 8-20 tasks.