subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
Install with Tessl CLI
npx tessl i github:projectbluefin/dakota --skill subagent-driven-developmentOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 99%
↑ 1.34xAgent success when using this skill
Validation for skill structure
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 severely lacking in specificity and actionable detail. It fails to explain what concrete actions the skill performs, relying entirely on abstract concepts like 'implementation plans' and 'independent tasks.' The description would not help Claude distinguish this skill from other task execution or planning skills.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Executes multiple code changes in parallel, runs independent test suites simultaneously, processes batch file operations').
Include natural trigger terms users would actually say (e.g., 'parallel execution', 'run these at the same time', 'batch processing', 'concurrent tasks').
Clarify the 'when' clause with explicit scenarios (e.g., 'Use when the user has a list of non-dependent tasks to complete, mentions parallel work, or when a plan contains steps that can run simultaneously').
| 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 used by users. Missing common variations or natural language triggers. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'implementation plans with independent tasks' provides some specificity around parallelizable work, but 'current session' is generic and could overlap with many task execution 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 document with excellent workflow clarity and actionability. The two-stage review process is well-documented with clear validation checkpoints and feedback loops. The main weakness is some verbosity in the advantages section and example workflow that could be tightened without losing clarity.
Suggestions
Trim the 'Advantages' section - many points are self-evident from the process description or could be condensed into a brief comparison table
Shorten the example workflow to show one complete task cycle plus a brief note that subsequent tasks follow the same pattern
| 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 specific prompt template references, clear process steps, and a detailed example workflow showing exact dialogue patterns. The integration section clearly names required skills and when to use them. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit validation checkpoints (spec compliance review → code quality review), clear feedback loops (reviewer finds issues → implementer fixes → re-review), and explicit sequencing via dot diagrams. Red flags section reinforces critical validation points. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, decision diagram for when to use, process diagram, and references to external prompt templates (./implementer-prompt.md, etc.) and related skills. Content is appropriately split with one-level-deep references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.