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.

2.40x

Quality

51%

Does it follow best practices?

Impact

96%

2.40x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/conductor/skills/track-management/SKILL.md

Quality

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 managing tracks entail?) and could benefit from more natural trigger terms that users would actually say when needing this skill.

Suggestions

List specific concrete actions such as 'create spec files, generate implementation plans, update track status, close completed tracks' to improve specificity.

Add natural trigger terms users might say, such as 'start a new feature', 'plan implementation', 'write a spec', 'track a bug fix' to improve discoverability.

Dimension	Reasoning	Score
Specificity	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	Explicitly answers both 'what' (creating, managing, working with Conductor tracks including spec.md, plan.md, and lifecycle operations) and 'when' ('Use this skill when creating, managing, or working with Conductor tracks'). The 'Use when' clause is present and clear.	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 specification'.	2 / 3
Distinctiveness Conflict Risk	The description is clearly scoped to 'Conductor tracks' with specific file references (spec.md, plan.md) and a defined domain (track 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 full project management handbook than a concise skill reference, explaining many concepts Claude already knows (track types, dependency categories, sizing heuristics). The templates and status marker conventions are genuinely useful, but the content would benefit enormously from being split into referenced files and trimmed of explanatory padding.

Suggestions

Extract the spec.md template, plan.md template, metadata.json schema, tracks.md format, and quality checklists into separate referenced files to reduce the SKILL.md to a concise overview with navigation links.

Remove explanatory sections that describe concepts Claude already knows: track types definitions, dependency type explanations, sizing guidelines rationale, and generic best practices like 'keep tracks focused'.

Add concrete tool usage examples for track operations — instead of 'Run /conductor:new-track', show the actual file creation commands, directory structure creation, and specific file writes that need to happen.

Add explicit validation/feedback loops: what specific checks to run after creating a spec, how to verify a plan covers all spec requirements, and what to do when checkpoint approval fails.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Extensively explains concepts Claude already understands (what a track is, what features/bugs/refactors are, sizing guidelines, dependency types). Much of this is generic project management knowledge that doesn't need to be spelled out. The track types section, sizing guidelines, dependency handling, and best practices sections are largely redundant with Claude's existing knowledge.	1 / 3
Actionability	Provides concrete templates for spec.md, plan.md, metadata.json, and tracks.md which are useful and copy-paste ready. However, the actual operations (creating, completing, reverting tracks) reference commands like `/conductor:new-track` and `/conductor:revert` without explaining what these do mechanically. The guidance is more descriptive than executable — it tells you the structure but not the specific tool calls or file operations to perform.	2 / 3
Workflow Clarity	The track lifecycle is sequenced (Creation → Implementation → Completion) and phase completion has explicit steps including verification and checkpoint approval. However, validation checkpoints are described at a high level ('Wait for checkpoint approval') without specifying how to validate or what constitutes passing. The revert operation lacks detail on error recovery. Missing concrete feedback loops for when things go wrong.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with no references to external files despite being a complex, multi-faceted skill. The spec.md template, plan.md template, metadata.json schema, tracks.md format, quality checklists, and common patterns could all be separate referenced files. Everything is inlined, making the skill extremely long and hard to navigate. No bundle files are provided to offload content to.	1 / 3
	Total	6 / 12 Passed

Validation

81%

Warnings & errors only

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: 112197c

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.