Resolves task dependencies, generates machine-actionable delegation specs, and structures phased subtask plans for multi-agent work. Use when writing delegation specs, resolving task dependencies, building phased subtask plans for multi-agent work, assigning work to sub-agents, or partitioning a feature into parallelizable phases.
100
100%
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, provides explicit trigger guidance via a 'Use when...' clause, and occupies a distinct niche in multi-agent task orchestration. The description is concise, uses third-person voice correctly, and includes varied natural trigger terms that cover the likely ways a user would invoke this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'resolves task dependencies', 'generates machine-actionable delegation specs', and 'structures phased subtask plans'. These are distinct, concrete capabilities rather than vague language. | 3 / 3 |
Completeness | Clearly answers both 'what' (resolves dependencies, generates delegation specs, structures phased plans) and 'when' with an explicit 'Use when...' clause listing five distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'delegation specs', 'task dependencies', 'subtask plans', 'multi-agent work', 'sub-agents', 'parallelizable phases', 'assigning work', 'partitioning a feature'. These cover multiple natural phrasings a user might employ. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around multi-agent task delegation and dependency resolution. Terms like 'delegation specs', 'sub-agents', and 'parallelizable phases' are highly specific and unlikely to conflict with general project management or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that efficiently communicates a complex multi-agent task decomposition workflow. It uses compact notation, decision trees, and tables to maximize information density while maintaining clarity. The content is highly actionable with concrete examples, explicit partition rules, and machine-ready delegation spec templates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It uses tables, decision trees, and compact notation (e.g., `TaskB → TaskA`) instead of verbose prose. No unnecessary explanations of concepts Claude already knows. | 3 / 3 |
Actionability | Provides concrete, actionable artifacts: a complete delegation spec template with all fields, a decision tree for delegation mechanism selection, specific examples of strong vs weak prompts, partition rules with exact paths, and a phased planning pattern. Everything is directly usable. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit phases. The dependency resolution section provides a clear algorithm (topological sort), cycle detection with a resolution strategy, and the mixed delegation table shows a clear 6-phase workflow. The Foundation-First Pattern includes explicit partition rules and dependency constraints. | 3 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections, uses a table for the delegation spec rather than inline walls of text, and appropriately references external files one level deep (REFERENCE.md for full template, project-consistency skill for Foundation Phase details, LESSONS-LEARNED.md for context). | 3 / 3 |
Total | 12 / 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.
18c6f2c
Table of Contents
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.