agentsclimarketplace

Track management

Skill FridrichMethod/awesome-skills/skills/track-management

Curated, auto-synced collection of 2,000+ Claude Code & Codex skills for AI4Protein, bioinformatics, AI development, and academic paper writing. One curl command installs them all.

Install
npx -y skills add FridrichMethod/awesome-skills --skill track-management

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.6 KB, 291 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it: 1 file

12.1 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.