Groups plan phases/tasks into dependency-ordered waves for parallel subagent execution via git worktrees. Analyses task dependencies, builds a DAG, assigns tasks to waves, and emits a living wave document that tracks status as work lands. Also updates an existing wave plan when tasks complete.
94
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific capabilities (DAG construction, topological sorting, wave document generation) and provides explicit trigger guidance with a comprehensive list of natural user phrases. The domain is highly specific and distinctive, making it easy for Claude to select this skill appropriately without confusion with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: builds a task dependency DAG, assigns wave numbers via topological sort, emits a living wave document that tracks status, and updates wave progress when tasks complete. | 3 / 3 |
Completeness | Clearly answers both 'what' (groups plan phases into dependency-ordered waves, builds DAG, assigns wave numbers, emits wave document, updates progress) and 'when' with an explicit 'Use when asked to:' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'group tasks into waves', 'plan parallel execution', 'schedule worktrees', 'wave breakdown', 'wave planning', 'dependency grouping', 'update wave statuses', 'parallel subagents', and 'which tasks can run in parallel'. These cover many natural phrasings a user might use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around wave-based parallel execution planning via git worktrees and dependency DAGs. The specific terminology (waves, worktrees, topological sort, subagent execution) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent workflow clarity and progressive disclosure. The two modes are clearly delineated with concrete steps, verification gates, and explicit anti-patterns. Minor verbosity in the principles and anti-pattern explanations (WHY lines) could be trimmed, but overall the content is actionable and well-organized.
Suggestions
Trim the WHY explanations in the anti-patterns section — Claude can infer why dependent tasks shouldn't share a wave or why verification matters; a single-line anti-pattern statement is sufficient.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some sections that could be tightened — the 'When not to use' section and some of the anti-patterns explain reasoning Claude could infer. The core principles section also restates concepts that are implicit in the workflow. However, it avoids explaining basic concepts like what DAGs or worktrees are, which is good. | 2 / 3 |
Actionability | Both Mode A and Mode B provide concrete, sequenced steps with specific file paths, bash commands for verification gates, and clear output expectations. The recognition example with input/output skeleton gives Claude a concrete model to follow. Status transitions are explicitly defined with a state diagram. | 3 / 3 |
Workflow Clarity | Both modes have clearly numbered steps with explicit validation checkpoints — Mode A step 7 validates task placement, Mode B step 2 runs verification gates before advancing. The anti-patterns section reinforces the gate-before-advance principle. Status transitions are clearly defined with a state machine diagram including the Blocked path. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to wave-format.md, dependency-analysis.md, status-tracking.md, and a YAML template. The main document contains enough to understand the workflow without needing to read references, while detailed format specs and protocols are appropriately externalized. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents