track-management

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

2|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/monang404/lunawave --skill track-management-monang404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: track-management
Source: https://github.com/monang404/lunawave/tree/main/.agent/skills/track-management
Command: npx skills add https://github.com/monang404/lunawave --skill track-management-monang404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Organizing features, bugs, and refactors into coherent, trackable work units is difficult without a consistent structure. This Skill standardizes how Conductor tracks are specified, planned, executed, and completed so progress stays visible and reversible. ## Core Features & Use Cases - Track Creation & Registration: Generate spec.md and plan.md files, assign track IDs in the {shortname}_{YYYYMMDD} format, and register entries in the tracks.md registry. - Lifecycle & Status Management: Apply consistent status markers ([ ], [~], [x], [-], [!]), record commit SHAs, and manage checkpoints across phases. - Templates & Quality Checklists: Use structured templates for specifications, plans, metadata.json, and track patterns for features, bugs, and refactors. - Use Case: When starting a new user-authentication feature, create a user-auth_20250115 track with a full specification, a three-phase plan, and registry entry, then update task markers as implementation progresses. ## Quick Start Ask the assistant to create a new Conductor track for your feature, including its spec.md, plan.md, and tracks.md registry entry.

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 for a feature?▼

Gather requirements through Q&A, then generate a spec.md with functional requirements and acceptance criteria, followed by a plan.md with phased tasks. Register the track in tracks.md with an ID like `user-auth_20250115` and create its metadata.json.

What is the Conductor track ID format?▼

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, for example `fix-login-error_20250115`.

What status markers should I use in a plan.md file?▼

Use `[ ]` for pending, `[~]` for in progress, `[x]` for complete with a commit SHA, `[-]` for intentionally skipped, and `[!]` for blocked tasks with the blocking reason noted.

How do I handle a blocked track in Conductor?▼

Mark blocked tasks with `[!]` and the reason, update the track status in tracks.md, and document the blocker in metadata.json. If the blocker is substantial, consider creating a separate dependency 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 about one week of work. Right-sized tracks complete in 1-5 days with 2-4 phases and 8-20 tasks.