subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
56
46%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/subagent-driven-development/SKILL.mdQuality
Discovery
7%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 description fails to communicate what the skill actually does - it only provides a vague trigger condition without explaining capabilities. The language is abstract and technical rather than action-oriented, making it difficult for Claude to know when to select this skill or what it accomplishes.
Suggestions
Add specific concrete actions this skill performs (e.g., 'Parallelizes task execution, coordinates multiple independent work items, tracks completion status')
Include natural trigger terms users would say (e.g., 'parallel tasks', 'run simultaneously', 'batch processing', 'concurrent execution')
Clarify the 'what' before the 'when' - describe the capability first, then specify trigger conditions with user-facing language
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'executing implementation plans' and 'independent tasks' without specifying concrete actions. No specific capabilities are listed. | 1 / 3 |
Completeness | While it attempts a 'Use when' clause, the 'what' is extremely weak (no concrete actions described), and the 'when' is vague and circular - it doesn't explain what triggers this skill. | 1 / 3 |
Trigger Term Quality | The terms 'implementation plans' and 'independent tasks' are technical jargon unlikely to be naturally spoken by users. Missing common variations or natural language triggers. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'independent tasks in the current session' provides some specificity that distinguishes it from general task execution, but 'implementation plans' is still broad enough to overlap with many development-related skills. | 2 / 3 |
Total | 5 / 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 strong skill with excellent workflow clarity and actionability. The DOT diagrams effectively communicate the process flow, and the example workflow provides concrete guidance. The main weakness is some verbosity in the Advantages and Red Flags sections that could be tightened without losing clarity.
Suggestions
Trim the 'Advantages' section - many points are self-evident from the process description and don't add new information
Consolidate the 'Red Flags' section by removing obvious points (e.g., 'Don't rush them into implementation') that Claude would naturally understand
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the 'Advantages' section repeats concepts already clear from the process, and the 'Red Flags' section is extensive with some obvious points Claude would know. | 2 / 3 |
Actionability | Provides concrete, executable guidance with clear process flows via DOT diagrams, specific prompt template references, and a detailed example workflow showing exact interactions and expected outputs. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit validation checkpoints (spec compliance review → code quality review), clear feedback loops for fixing issues, and explicit sequencing via DOT diagrams showing the complete process. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, references to external prompt templates (./implementer-prompt.md, etc.), and links to related skills. Content is appropriately split with one-level-deep references clearly signaled. | 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.
- Repository
- roman01la/skills-agents
- Commit
45417f2
- 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.