skills.rest
leonardoteodoroo
leonardoteodorooCOMMUNITY
Explore all skills by this author →
GitHub

track-management

Coordinate Conductor tracks across spec.md, plan.md, and lifecycle stages.

Updated Feb 3, 2026
Search Tags:#workflow#planning#metadata#lifecycle#conductor#project-tracking#track-management
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill track-management-leonardoteodoroo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: track-management
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/track-management
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill track-management-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track management provides a structured approach to organizing, tracking, and completing work items as tracks across spec, plan, and lifecycle events.

Core Features & Use Cases

  • Defines and manages Track IDs: consistent naming following shortname_YYYYMMDD pattern and registry updates.
  • Lifecycle guidance: from creation to completion with phases and verification.
  • Documentation alignment: ensures spec.md, plan.md, and track metadata stay synchronized.

Quick Start

Create a new track by defining its Track ID and drafting the initial spec and plan.

Frequently Asked Questions about track-management

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

FAQPage Schema
How do I coordinate Conductor tracks for features, bugs, and refactors?▼

Coordinate Conductor tracks by enforcing consistent track IDs, registry entries, and status markers. This ensures spec.md, plan.md, and track metadata stay synchronized across the entire project lifecycle from creation to completion.

What is the standard naming pattern for track management IDs?▼

Track management uses a shortname_YYYYMMDD naming pattern for track IDs. This convention maintains registry consistency and synchronizes metadata across spec.md and plan.md documentation throughout the lifecycle.

How does metadata synchronization work between spec.md and plan.md during lifecycle operations?▼

Metadata synchronization aligns spec.md, plan.md, and track metadata by enforcing registry entries and status markers. It maintains documentation consistency across all lifecycle phases from initial track creation through final completion.

Can I manage track lifecycles without updating the registry entries?▼

No, track management enforces registry updates alongside status markers and metadata synchronization. Registry entries are required to maintain consistent workflows across spec.md, plan.md, and lifecycle operations from creation to completion.

What's the best way to structure project-tracking workflows for multiple work item types?▼

Structure project-tracking by organizing features, bugs, and refactors into distinct Conductor tracks. Apply consistent track IDs, registry entries, and lifecycle phases to keep spec.md and plan.md metadata synchronized.

When do I need to enforce track IDs and status markers for workflow planning?▼

Enforce track IDs and status markers whenever initiating lifecycle operations for features, bugs, or refactors. This discipline ensures spec.md, plan.md, and track metadata remain synchronized from creation through completion.

Related Skills

Explore More Product & Management Skills→
emilneuraz-aiemilneuraz-ai

track-management

Create, track, and complete Conductor tracks with spec.md, plan.md, and tracks.md.

Community
Advanced
ArogyaReddyArogyaReddy

track-management

Organize Conductor tracks from spec to completion with lifecycle tracking.

Community
Advanced
Sumeet138Sumeet138
1

track-management

Organize Conductor tracks with spec.md, plan.md, and tracks.md.

Community
Advanced
edithatogoedithatogo
1

conductor-newtrack

Generate spec.md, plan.md, and track metadata for new Conductor tracks.

Community
Intermediate