Index of every page on this site: llms.txt
All skills
wshobson avatar

/track-management

@4220308
by Seth Hobsonwshobson/agents43k stars
4,518
Run it yourself

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.

  • 2 files
  • 13.7 KB
  • Updated 6 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/wshobson/agents/track-management

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈53 tokens for metadata: the name and description. ≈357 when used: this file. ≈3.1k more on demand in 1 file.

Description uses 2.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈212 characters, or 2.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 4220308. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 6 months ago
version
1.0.0
  • Refactoring
  • conductor
  • track-management
  • spec
  • planning
  • workflow
  • features
  • bugs

README badge

README badge for wshobson/agents/track-management

Manages Conductor tracks — the logical work units organizing features, bugs, and refactors through specification, planning, and implementation phases. Covers track creation, spec.md and plan.md workflows, lifecycle management, and the tracks.md registry.

Generated from the current SKILL.md.

What is a Conductor track?
A track is a logical work unit that organizes a single feature, bug, or refactor through specification, planning, and implementation phases. It uses spec.md and plan.md files to define requirements and execution steps.
When should I create a new track versus adding to an existing one?
Create a new track for each distinct logical change. The skill emphasizes one track, one concern — if the work touches multiple unrelated areas, split it into separate tracks.
What markers and conventions does this skill use?
The skill defines status markers and conventions for tracks, spec.md, and plan.md files. Consult references/details.md for the complete pattern documentation and worked examples.
Do I need to record commit SHAs when completing tasks?
Yes. The skill requires you to note commit SHAs for completed tasks as part of tracking progress and maintaining a record for reference.

Generated from the current SKILL.md. These answers refresh after source changes.