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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/conductor/skills/track-management/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and lean with excellent progressive disclosure via a single real reference file. Its weaknesses are that the actionable structural details (file formats, marker syntax) are deferred rather than shown inline, and the track lifecycle is never laid out as an explicit sequenced workflow.

Suggestions

Add a short 'Track lifecycle' section that sequences the phases (create → spec → plan → implement → verify → archive) with explicit validation checkpoints, rather than only implying the order through best practices.

Inline a minimal example of spec.md/plan.md structure and the status marker syntax so the body is self-sufficient for the most common cases without requiring references/details.md.

Trim or merge the intro paragraph with the frontmatter description to remove the slight repetition of the 'logical work units for features, bugs, and refactors' framing.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding of concepts Claude already knows; the only mild redundancy is the intro paragraph restating the frontmatter description with the phase framing, which keeps it just below anchor 5.	4 / 5
Actionability	Best Practices give concrete numeric guidance ('3-5 tasks maximum', '1-5 days of work', 'Record SHAs'), but the key structural details (spec.md/plan.md format, status marker syntax) are absent from the body and deferred to the reference, leaving gaps.	3 / 5
Workflow Clarity	A track lifecycle is implied through best-practice ordering hints ('Review specs before planning', 'Verification after phases'), but there is no explicit sequenced workflow with checkpoints in the body, matching the anchor where steps/validation are present but incomplete.	3 / 5
Progressive Disclosure	A clear overview ('When to Use', 'Best Practices') points to a single well-signaled one-level-deep reference ('references/details.md'), which exists as a real file, with content appropriately split.	5 / 5
	Total	15 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 is strong: it explicitly states both what the skill covers and when to use it, with concrete trigger terms and a distinct niche. The only soft spot is that the action verbs (creating, managing, working with) are slightly generic relative to a fully comprehensive action list.

Dimension	Reasoning	Score
Specificity	Names the domain plus several actions ('creating, managing, or working with') and concrete artifacts ('spec.md, plan.md, and track lifecycle operations'), but the verbs themselves are somewhat generic, so it sits above anchor 3 rather than at 5.	4 / 5
Completeness	Explicitly answers 'when' via 'Use this skill when creating, managing, or working with...' and 'what' via 'logical work units for features, bugs, and refactors' plus the file/lifecycle scope, with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('Conductor tracks', 'features, bugs, and refactors', 'spec.md', 'plan.md'), but misses some synonyms/registry terms like 'tracks.md' that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	'Conductor tracks' with spec.md/plan.md/lifecycle is a clearly distinct niche with minimal overlap risk against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: wshobson/agents
Path: plugins/conductor/skills/track-management/SKILL.md
Commit: d6837ae

Reviewed: about 12 hours 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.