Name: track-management
Author: wshobson

Imported from wshobson/agents (plugins/conductor/skills/track-management/SKILL.md) via skills.sh. Install upstream with npx skills add wshobson/agents --skill track-management. Copyright stays with the author.

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

One track, one concern: Keep tracks focused on a single logical change
Small phases: Break work into phases of 3-5 tasks maximum
Verification after phases: Always include verification tasks
Update markers immediately: Mark task status as you work
Record SHAs: Always note commit SHAs for completed tasks
Review specs before planning: Ensure spec is complete before creating plan
Link dependencies: Explicitly note track dependencies
Archive, don't delete: Preserve completed tracks for reference
Size appropriately: Keep tracks between 1-5 days of work
Clear acceptance criteria: Every requirement must be testable

Install track-management and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "wshobson-agents-track-management", "kind": "skill", "name": "track-management", "description": "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.", "publisher": "wshobson", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/wshobson/agents", "path": "plugins/conductor/skills/track-management/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/wshobson/agents/track-management", "key": "wshobson/agents/plugins/conductor/skills/track-management/SKILL.md" } }, "instructions": "# Track Management\n\nGuide for creating, managing, and completing Conductor tracks - the logical work units that organize features, bugs, and refactors through specification, planning, and implementation phases.\n\n## When to Use This Skill\n\n- Creating new feature, bug, or refactor tracks\n- Writing or reviewing spec.md files\n- Creating or updating plan.md files\n- Managing track lifecycle from creation to completion\n- Understanding track status markers and conventions\n- Working with the tracks.md registry\n- Interpreting or updating track metadata\n\n## Detailed patterns and worked examples\n\nDetailed", "cost": { "context_tokens": 356 } }

track-management

About