AutoGineer
Generated banner for Track Management
Generated logo for Track Management

Track Management

Seth HobsonCommunityCreated by Seth Hobson

  • Skill
  • Guidelines
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
— the description by Seth Hobson

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Track Management provides a standardized methodology for organizing software development tasks into logical units called tracks. It covers the entire lifecycle of a feature, bug, or refactor, ensuring that work is clearly defined through specifications, broken down into manageable phases, and tracked for progress and verification. By utilizing specific file structures like spec.md and plan.md, this skill helps maintain consistency, traceability, and focus throughout the development process.

What it does

  • Defines requirements and acceptance criteria for new features, bugs, or refactors.
  • Structures work into phased plans with clear, testable tasks.
  • Maintains a registry of active and completed work units.
  • Provides a lifecycle process from initial specification to final verification.
  • Ensures traceability by linking tasks to commit SHAs.
  • Facilitates documentation updates upon track completion.

When to use it

  • When initiating a new feature, bug fix, or refactoring effort.
  • When you need to define clear scope and acceptance criteria for a task.
  • When breaking down complex work into smaller, manageable phases.
  • When you need to track the status and progress of development tasks systematically.
  • When you need to ensure verification steps are included in the development workflow.

Advantages

  • Promotes focused development by limiting tracks to single concerns.
  • Improves project visibility through structured status tracking.
  • Ensures testability by requiring explicit acceptance criteria.
  • Facilitates better team coordination and historical reference.
  • Reduces technical debt by enforcing clear planning and documentation.

Usage examples

“Create a new feature track for adding user authentication.”
The agent will guide you through defining requirements, generating a spec.md, creating a phased plan.md, and registering the track in tracks.md.
“How do I structure the plan for my current bug fix?”
The agent will help you break the work into 3-5 task phases, include verification steps, and ensure you are ready to track progress with commit SHAs.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/wshobson/track-management/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip track-management.zip -d .agents/skills

Documentation by Seth Hobson

Track Management

Guide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.

When to Use This Skill

  • Creating new feature, bug, or refactor tracks

  • Writing or reviewing spec.md files

  • Creating or updating plan.md files

  • Managing track lifecycle from creation to completion

  • Understanding track status markers and conventions

  • Working with the tracks.md registry

  • Interpreting or updating track metadata

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

  1. One track, one concern: Keep tracks focused on a single logical change

  2. Small phases: Break work into phases of 3-5 tasks maximum

  3. Verification after phases: Always include verification tasks

  4. Update markers immediately: Mark task status as you work

  5. Record SHAs: Always note commit SHAs for completed tasks

  6. Review specs before planning: Ensure spec is complete before creating plan

  7. Link dependencies: Explicitly note track dependencies

  8. Archive, don't delete: Preserve completed tracks for reference

  9. Size appropriately: Keep tracks between 1-5 days of work

  10. Clear acceptance criteria: Every requirement must be testable

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Seth Hobson
Publisher
Seth Hobson (Community)
Source
wshobson/agents · plugins/conductor/skills/track-management · commit 4bde316
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Seth Hobson or Seth Hobson.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download track-management.zip