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

—

Does it follow best practices?

Impact

96%

2.40x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

The skill is highly actionable with concrete templates, formats, and thresholds, and its main lifecycle workflow is well-sequenced with checkpoints. It loses points for verbosity/redundancy, a missing validation loop on the destructive revert path, and a monolithic structure with no progressive disclosure.

Suggestions

Consolidate the overlapping Track Lifecycle and Track Operations sections, and merge the spec/plan quality checklists into their template sections to remove redundancy.

Add an explicit validation feedback loop to 'Reverting a Track' (e.g. verify no active dependent tracks, confirm checkpoint, then re-run validation) before the destructive step.

Move the large file templates (spec.md, plan.md, metadata.json) and the common track patterns into reference files (e.g. references/SPEC_TEMPLATE.md) linked one level deep from SKILL.md to enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The ~594-line body is domain-specific rather than explaining concepts Claude already knows, but it is padded with redundancy — the Track Lifecycle and Track Operations sections overlap, and the quality checklists duplicate the spec/plan templates — so it could be tightened considerably.	2 / 3
Actionability	Provides copy-paste-ready templates (spec.md, plan.md, metadata.json, tracks.md), an exact track ID format with examples, a status-marker table, concrete numeric sizing thresholds, and explicit slash commands.	3 / 3
Workflow Clarity	The lifecycle is clearly sequenced with verification tasks and checkpoint approval, but the destructive 'Reverting a Track' operation has no explicit validate/verify feedback loop, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned but monolithic: no bundle/reference files exist and content that could be split out (file templates, checklists, common patterns) is all inline, so it is not a lean overview pointing to one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 has an explicit trigger clause, clear natural terms (spec.md, plan.md, feature/bug/refactor), and defines its niche. Its main weakness is generic action verbs and moderate overlap risk with other Conductor track skills.

Suggestions

Replace generic verbs ('managing, working with') with more concrete track-specific actions (e.g. 'scaffold, plan, status, and revert tracks') to lift specificity.

Narrow the scope language to reduce overlap with sibling Conductor skills, e.g. 'Use for the spec/plan authoring and lifecycle bookkeeping of a single track' rather than all 'track lifecycle operations'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Conductor tracks', 'features, bugs, and refactors') and actions ('creating, managing, or working with'), but the verbs are generic rather than concrete like 'extract/fill/merge', so it stops short of comprehensive specific actions.	2 / 3
Completeness	An explicit 'Use this skill when…' clause answers when, and 'Conductor tracks…Applies to spec.md, plan.md, and track lifecycle operations' answers what, satisfying both halves.	3 / 3
Trigger Term Quality	Includes natural terms a user would say — 'spec.md', 'plan.md', 'features, bugs, and refactors', and 'Conductor tracks' — giving good coverage across the domain.	3 / 3
Distinctiveness Conflict Risk	'Conductor tracks' is a clear niche, but the broad 'creating, managing, or working with…track lifecycle operations' scope overlaps with sibling Conductor skills (e.g. new-track, revert) referenced in the body.	2 / 3
	Total	10 / 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 — 13 / 16 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
relative_links	Relative link issues: 4 missing	Warning

	Total	13 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Commit: abece4a

Reviewed: 4 days 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.