subagent-driven-development

Use when executing implementation plans with independent tasks in the current session

Quality

47%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/subagent-driven-development/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured orchestration skill with excellent workflow clarity and strong actionability. The process is clearly sequenced with proper validation gates and error recovery paths. However, it suffers from verbosity — the Advantages section, lengthy example, and some explanatory text could be significantly trimmed or moved to supporting files to improve token efficiency.

Suggestions

Trim or remove the Advantages section entirely — Claude doesn't need to be sold on why to use the skill it's already been told to use

Shorten the example workflow to show just one task cycle (dispatch → review → fix → approve) instead of two full tasks plus commentary

Move the 'When to Use' decision tree and Integration section to a separate reference file, keeping only a one-line trigger description in the main skill

Dimension	Reasoning	Score
Conciseness	The skill contains significant verbosity, especially in the Advantages section which lists benefits Claude doesn't need explained, the lengthy example workflow that could be shorter, and the dot graph diagrams which are bulky representations. The 'Why subagents' explanation and some Red Flags items are somewhat redundant. However, the core process and status handling sections are reasonably efficient.	2 / 3
Actionability	The skill provides concrete, actionable guidance: clear process steps, specific status codes with handling instructions, references to prompt templates, model selection criteria with specific signals, and a detailed example workflow showing exact interactions. The TodoWrite tool usage and subagent dispatch patterns are specific enough to execute.	3 / 3
Workflow Clarity	The workflow is exceptionally clear with explicit sequencing via the dot graph, validation checkpoints (spec compliance review THEN code quality review), feedback loops (reviewer finds issues → implementer fixes → re-review), and clear error handling for all four implementer statuses. The Red Flags section explicitly calls out ordering constraints like not starting code quality review before spec compliance passes.	3 / 3
Progressive Disclosure	The skill references prompt templates (./implementer-prompt.md, ./spec-reviewer-prompt.md, ./code-quality-reviewer-prompt.md) and other skills appropriately, but no bundle files were provided to verify these exist. The main SKILL.md itself is quite long (~200+ lines) with sections like the full example workflow and Advantages that could be split into separate files. The 'When to Use' decision tree and Integration section are well-structured.	2 / 3
	Total	10 / 12 Passed

Description

17%

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 vague and abstract to be useful for skill selection. It lacks concrete actions, natural trigger terms, and specificity about what kind of implementation plans or tasks it handles. While it includes a 'Use when' clause, the content within it is not descriptive enough to distinguish this skill from others.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Parallelizes independent subtasks from a plan, executes them concurrently, and aggregates results' instead of the vague 'executing implementation plans'.

Include natural trigger terms users would actually say, such as 'parallel execution', 'run tasks simultaneously', 'batch processing', 'concurrent tasks', or 'multi-step plan'.

Clarify the 'what' portion by describing the mechanism (e.g., task parallelization, orchestration) and the types of tasks it handles to distinguish it from general task execution skills.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'executing implementation plans' and 'independent tasks' without specifying any concrete actions. There are no specific capabilities listed—just abstract concepts.	1 / 3
Completeness	It has a 'Use when...' clause addressing the 'when' question, but the 'what does this do' part is extremely weak—'executing implementation plans with independent tasks' barely describes what the skill actually does or how it works.	2 / 3
Trigger Term Quality	The terms 'implementation plans' and 'independent tasks' are not natural phrases users would say. Users are more likely to say things like 'run these tasks in parallel' or 'execute my plan'. The language is overly abstract and jargon-heavy.	1 / 3
Distinctiveness Conflict Risk	'Executing implementation plans' and 'independent tasks' are so generic that this could overlap with virtually any task execution, project management, or workflow skill. There are no distinct triggers to differentiate it.	1 / 3
	Total	5 / 12 Passed

Validation

100%

Warnings & errors only

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: obra/superpowers
Commit: 6fd4507

Reviewed: 16 days ago

Table of Contents

Discovery Implementation Validation

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.