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 ./tests/ext_conformance/artifacts/agents-wshobson/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 specificity in listing concrete actions and could benefit from more natural trigger terms that users would actually say. The domain-specific terminology (Conductor tracks) helps with distinctiveness but may limit discoverability.
Suggestions
List specific concrete actions such as 'create spec files, generate implementation plans, update track status, close completed tracks' instead of the generic 'creating, managing, or working with'.
Add more natural trigger terms users might say, such as 'start a new feature', 'plan implementation', 'write a specification', 'track a bug fix', or 'organize work'.
| 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'). Has a clear 'Use when...' clause. | 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 lifecycle operations, making it highly distinctive and 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 documentation manual than a concise skill reference, with extensive explanatory content that Claude doesn't need (track types, sizing guidelines, dependency concepts). The templates are useful but should be extracted into separate files, with the main skill providing a lean overview and clear navigation.
Suggestions
Extract the spec.md template, plan.md template, tracks.md format, and metadata.json schema into separate referenced files (e.g., SPEC_TEMPLATE.md, PLAN_TEMPLATE.md) and link to them from a concise overview.
Remove explanatory sections like 'Track Concept', 'Track Types' descriptions, and 'Track Sizing Guidelines' - Claude understands these concepts and can infer appropriate sizing.
Add concrete validation steps with actual commands or checks (e.g., 'Verify all [ ] markers resolved before marking phase complete') rather than abstract instructions like 'Wait for checkpoint approval'.
Consolidate the two quality checklists and best practices into a single compact reference section, removing redundancy between them.
| 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 markdown templates for spec.md, plan.md, tracks.md, and metadata.json which are copy-paste ready. However, the actual operations (creating, completing, reverting tracks) reference commands like `/conductor:new-track` and `/conductor:revert` without showing what those commands do internally. 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 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 - templates, checklists, patterns, best practices, metadata schemas, and guidelines all in one massive file. Content like the full spec.md template, plan.md template, metadata.json schema, and common track patterns should be split into separate referenced files. No external file references are used despite the content clearly warranting them. | 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
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- 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.