track-management
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.
66
51%
Does it follow best practices?
Impact
96%
2.40xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/conductor/skills/track-management/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has good completeness with an explicit 'Use when' clause and is distinctive enough to avoid conflicts with other skills. However, it lacks specific concrete actions (what exactly does it do with tracks?) and could benefit from more natural trigger terms that users would actually say. The specificity of capabilities is moderate—it tells you the domain but not the detailed operations.
Suggestions
Add specific concrete actions like 'Creates spec.md files, generates implementation plans, updates track status, manages track lifecycle from creation to completion'.
Include more natural trigger terms users might say, such as 'start a new feature', 'plan a bug fix', 'write a spec', 'break down work into tasks'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain ('Conductor tracks') and mentions some artifacts (spec.md, plan.md, track lifecycle operations), but doesn't list specific concrete actions like 'create spec files', 'generate plans', 'update track status', etc. | 2 / 3 |
Completeness | Has an explicit 'Use this skill when...' clause covering the 'when' (creating, managing, or working with Conductor tracks) and addresses 'what' (logical work units for features, bugs, refactors; spec.md, plan.md, and track lifecycle operations). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'tracks', 'spec.md', 'plan.md', 'features', 'bugs', 'refactors', but these are somewhat tool-specific jargon. Missing natural user phrases like 'start a new feature', 'plan work', 'track progress', or 'create a spec'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to 'Conductor tracks' with specific file references (spec.md, plan.md) and lifecycle operations, making it unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is comprehensive in coverage but severely over-engineered for a SKILL.md file. It reads more like a complete project management methodology document than a concise skill reference. The templates and status marker conventions are genuinely useful, but they're buried in excessive explanatory content about concepts Claude already understands, and the entire document should be restructured with progressive disclosure to separate the overview from detailed templates and checklists.
Suggestions
Reduce the SKILL.md to a concise overview (~50-80 lines) covering track ID format, lifecycle summary, status markers, and key operations, then move templates (spec.md, plan.md, metadata.json, tracks.md) into separate referenced files like TEMPLATES.md
Remove explanatory sections that describe concepts Claude already knows: 'Track Concept' rationale, 'Track Types' descriptions of what features/bugs/refactors are, 'Track Sizing Guidelines' general advice about sizing
Add concrete validation commands or checks to the workflow steps - e.g., what specifically to verify before marking a phase complete, what tool commands to run, what constitutes a failed checkpoint
Consolidate the two quality checklists (spec and plan) into a separate CHECKLISTS.md file referenced from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Explains concepts Claude already understands (what a track is, what features/bugs/refactors are, what dependencies mean). Sections like 'Track Concept', 'Track Types', 'Track Sizing Guidelines', 'Handling Track Dependencies' are largely explanatory rather than instructional. The 'Track Concept' section explaining that tracks 'provide semantic organization' is unnecessary padding. | 1 / 3 |
Actionability | Provides concrete templates (spec.md, plan.md, metadata.json, tracks.md) which are useful and copy-paste ready. However, the actual operations sections ('Creating a Track', 'Completing a Phase') are high-level numbered lists referencing commands like `/conductor:new-track` without showing actual executable code or tool invocations. The guidance is structured but often descriptive rather than executable. | 2 / 3 |
Workflow Clarity | The track lifecycle is clearly sequenced (Creation → Implementation → Completion) with numbered steps, and verification tasks are mentioned within phases. However, validation checkpoints are implicit rather than explicit - there are no concrete validation commands or error recovery feedback loops. The 'Completing a Phase' section mentions 'Wait for checkpoint approval' without explaining what happens if approval fails. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with everything inline. The full spec.md template, plan.md template, metadata.json schema, tracks.md format, quality checklists, common patterns, sizing guidelines, dependency handling, and best practices are all in one massive file. Much of this content (templates, checklists, patterns) should be split into referenced files. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (594 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
27a7ed9
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.