subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
94
46%
Does it follow best practices?
Impact
99%
1.41xAverage score across 10 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.opencode/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 is too abstract and fails to communicate what the skill actually does. It relies on technical jargon ('implementation plans', 'independent tasks') without explaining concrete capabilities or providing natural trigger terms users would actually say. The description needs substantial improvement to help Claude select it appropriately.
Suggestions
Replace abstract language with concrete actions - specify what 'executing implementation plans' means (e.g., 'Runs multiple coding tasks in parallel', 'Coordinates batch file operations')
Add natural trigger terms users would say, such as 'parallel tasks', 'batch processing', 'run multiple', 'concurrent execution'
Expand the 'Use when...' clause with specific scenarios like 'Use when the user wants to run multiple independent operations simultaneously or process a list of tasks in parallel'
| 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 to answer 'when' with 'Use when...', the 'what' is extremely weak. 'Executing implementation plans' doesn't explain what the skill actually does or what capabilities it provides. | 1 / 3 |
Trigger Term Quality | The terms 'implementation plans' and 'independent tasks' are technical jargon unlikely to be naturally used 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 vague enough to potentially 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 that clearly defines a subagent-driven development workflow with excellent process clarity and validation checkpoints. The two-stage review system (spec compliance then code quality) is well-articulated with explicit feedback loops. Minor verbosity in the advantages section and lengthy example could be trimmed, but overall the skill provides actionable, well-organized guidance.
Suggestions
Consider condensing the 'Advantages' section - some points repeat what's already clear from the process description
The example workflow could be shortened while still demonstrating the key interactions and review loops
| 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 example workflow is quite lengthy. The dot diagrams add value but the text explanations sometimes duplicate what the diagrams show. | 2 / 3 |
Actionability | Provides concrete, actionable guidance with clear process steps, specific prompt template references, and a detailed example workflow showing exact interactions. The red flags section gives specific do/don't guidance that Claude can directly follow. | 3 / 3 |
Workflow Clarity | Excellent workflow clarity with explicit sequencing via dot diagrams, clear validation checkpoints (spec review then code quality review), and explicit feedback loops (reviewer finds issues → implementer fixes → re-review). The two-stage review process is well-defined with clear ordering constraints. | 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 between the main skill and referenced files, with one-level-deep navigation. | 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
- projectbluefin/dakota
- Commit
f062bf8
- 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.