track-management

Create and govern Conductor tracks with spec.md, plan.md, and tracks.md registry.

3|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/duanbiao2000/obsidianDoc26 --skill track-management-duanbiao2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: track-management
Source: https://github.com/duanbiao2000/obsidianDoc26/tree/main/agents-main/plugins/conductor/skills/track-management
Command: npx skills add https://github.com/duanbiao2000/obsidianDoc26 --skill track-management-duanbiao2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track management coordinates the end-to-end lifecycle of development work by turning features, bugs, and refactors into organized tracks with defined specs, plans, and lifecycle status.

Core Features & Use Cases

  • Create and govern tracks from inception to completion, with clear milestones.
  • Manage spec.md and plan.md artifacts, track lifecycle, and maintain a central registry.
  • Enforce consistent track IDs and metadata generation to support traceability.

Quick Start

Create a new track using the framework, generate its spec.md and plan.md, and register the track in 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 the lifecycle of software development tracks from creation to completion?

Track management coordinates software development tracks end-to-end by applying lifecycle markers, generating spec.md and plan.md artifacts, and maintaining a central tracks.md registry to govern tasks and statuses. It enforces consistent track IDs for full traceability.

What's the best way to organize feature specs and plans for multiple development tasks?

Organizing feature specs and plans is handled by generating structured spec.md and plan.md files for each track. This approach turns features and refactors into governed tracks with defined milestones and standardized metadata.

How do I create a central registry for tracking project workflow statuses?

Creating a central registry involves maintaining a tracks.md file that records track IDs and lifecycle markers. This registry coordinates all development tasks and their current statuses across the project workflow.

Can I generate standardized metadata for software features and bug fixes together?

Standardized metadata generation supports both features and bug fixes by creating consistent spec.md, plan.md, tracks.md, and metadata.json artifacts. This enforces uniform track IDs and lifecycle markers across all development work.

Does track management work without external project management dependencies?

Track management operates independently with no external dependencies. It uses internal lifecycle operations and metadata generation to coordinate tasks, statuses, and the tracks registry without requiring additional project management tools.

When do I need to update lifecycle markers in the tracks registry?

Lifecycle markers in the tracks registry should be updated whenever a development track changes status, from creation through completion. This ensures the tracks.md registry accurately reflects current task progress and maintains traceability.