decomposition
Resolves task dependencies, generates machine-actionable delegation specs, 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.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
85%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 description that clearly articulates specific capabilities and provides explicit trigger guidance via a 'Use when...' clause. Its main weakness is that the trigger terms lean toward technical jargon ('machine-actionable delegation specs', 'parallelizable phases') rather than natural language a user might actually type, which could reduce discoverability for less technical prompts about breaking down or coordinating work.
Suggestions
Add more natural-language trigger terms that users might actually say, such as 'break down tasks', 'split work across agents', 'coordinate parallel work', or 'plan task execution order'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'resolves task dependencies', 'generates machine-actionable delegation specs', 'structures phased subtask plans for multi-agent work'. These are distinct, concrete capabilities. | 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 trigger scenarios including delegation specs, dependency resolution, phased plans, sub-agent assignment, and feature partitioning. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'delegation specs', 'task dependencies', 'subtask plans', 'sub-agents', 'parallelizable phases', but these are somewhat specialized/technical. Common user phrasings like 'break down work', 'split tasks', 'coordinate agents', or 'task planning' are missing. | 2 / 3 |
Distinctiveness Conflict Risk | The description carves out 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 | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that efficiently communicates a complex multi-agent task decomposition workflow. Its greatest strengths are the compact notation, concrete templates, and clear decision trees that make it immediately actionable. The only notable weakness is that all content lives in a single file without bundle support, though the content length is reasonable enough that this is a minor issue.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It uses tables, compact notation (e.g., `TaskB → TaskA`), and terse examples rather than verbose explanations. No unnecessary preamble or concept explanations that Claude would already know. | 3 / 3 |
Actionability | Provides a complete, copy-paste-ready delegation spec template with all fields, concrete examples of strong vs weak prompts, a decision tree for delegation mechanism, and specific partition rules with exact paths. The guidance is immediately executable. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced: dependency resolution has an explicit algorithm (topological sort), phased delegation is laid out in a numbered table, the delegation mechanism uses a clear decision tree, and the Foundation-First Pattern specifies phase ordering with explicit dependency constraints. The 'common mistake' note serves as a validation checkpoint. | 3 / 3 |
Progressive Disclosure | The skill references external files (`.opencastle/LESSONS-LEARNED.md`, `project-consistency` skill) which is good, but all content is inline in a single file that's moderately long. The delegation spec template could potentially be split out. The reference to 'load project-consistency skill' is a good one-level-deep pointer, but there are no bundle files to support further disclosure. | 2 / 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.
- Repository
- monkilabs/opencastle
- Commit
7a69a05
- 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.