track-management

Manage Conductor track lifecycle from creation through completion.

Updated Dec 16, 2025
One-click install
npx skills add https://github.com/EanLee/article-write --skill track-management-eanlee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: track-management
Source: https://github.com/EanLee/article-write/tree/main/.github/skills/track-management
Command: npx skills add https://github.com/EanLee/article-write --skill track-management-eanlee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation, management, and lifecycle operations of Conductor tracks, ensuring organized and traceable work units for features, bugs, and refactors.

Core Features & Use Cases

  • Track Creation: Define requirements, generate specifications (spec.md), and create phased plans (plan.md).
  • Lifecycle Management: Track progress, update statuses, and manage completion or reversion of work units.
  • Use Case: When starting a new feature, use this skill to create a new track, define its requirements in spec.md, break down the work into phases in plan.md, and track its progress through implementation.

Quick Start

Use the track-management skill to create a new feature track.

Frequently Asked Questions about track-management

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

FAQPage Schema
How do I manage project workflows for features and bugs using structured specifications?

Manage project workflows by defining requirements in spec.md files and breaking down work into phased plans using plan.md. This organizes features, bugs, and refactors through defined lifecycle phases and status markers.

What is the best way to track implementation progress across multiple project phases?

Track implementation progress by updating status markers in tracks.md and metadata.json files. This manages the lifecycle from creation and planning through completion or reversion of work units.

How do I create a new track for a feature or refactor?

Create a new track by defining requirements to generate a spec.md specification, then break down the implementation work into a phased plan.md document for structured execution.

Does track management work without external project management dependencies?

Track management operates without external dependencies, relying entirely on structured local documentation in spec.md, plan.md, tracks.md, and metadata.json to organize and trace work units.

When do I need to use a track management workflow instead of a generic task list?

Use track management when organizing complex work units like features, bugs, and refactors that require defined phases, structured specifications, and traceable lifecycle status markers.

Can I revert or update the status of a work unit after implementation has started?

Update statuses and manage completion or reversion of work units by modifying the status markers tracked in metadata.json and tracks.md throughout the implementation lifecycle.