About track-management
A skill that guides the creation, planning, review, and completion of Conductor tracks for features, bugs, and refactors. It is for teams organizing work through specifications, plans, lifecycle statuses, and a track registry.
Key features
- 01Create feature, bug, and refactor tracks
- 02Write and review specifications
- 03Create and update plans
- 04Manage track lifecycle and status
- 05Maintain the tracks.md registry
Use cases
- 01Organize a new feature from specification to implementation
- 02Review a track plan
- 03Update track status and metadata
- 04Maintain the project track registry
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill track-managementAfter installing, type/track-managementin Claude Code to confirm it loaded.
Bundled filesresources/implementation-playbook.md
Details
From the project READMETrack 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.
Use this skill when
- 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
Do not use this skill when
- The task is unrelated to track management
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Resources
resources/implementation-playbook.mdfor detailed patterns and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Comments
Markdown supported