test-driven-development
tessl i github:obra/superpowers --skill test-driven-developmentUse when implementing any feature or bugfix, before writing implementation code
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
Implementation
85%This is a strong, actionable TDD skill with excellent workflow clarity and concrete examples. The verification checkpoints and feedback loops are well-defined. The main weakness is some redundancy between the 'Why Order Matters' explanations and the 'Common Rationalizations' table, which could be consolidated to improve token efficiency.
Suggestions
Consolidate 'Why Order Matters' and 'Common Rationalizations' sections to eliminate redundant content about tests-after, sunk cost, and pragmatism arguments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy—the 'Common Rationalizations' table largely repeats content from 'Why Order Matters' section. The repeated emphasis on 'delete and start over' appears multiple times. However, most content earns its place and assumes Claude's competence. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples, specific bash commands for verification, clear Good/Bad comparisons, and a concrete bug fix walkthrough. The examples are copy-paste ready and demonstrate real behavior. | 3 / 3 |
Workflow Clarity | The Red-Green-Refactor cycle is explicitly sequenced with mandatory verification checkpoints at each stage. The workflow includes clear feedback loops ('Test fails? Fix code, not test'), a visual diagram, and a comprehensive verification checklist before completion. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from overview to detailed workflow to troubleshooting. References external file (@testing-anti-patterns.md) appropriately for related but separate concerns. Content is appropriately organized without being monolithic. | 3 / 3 |
Total | 11 / 12 Passed |
Activation
15%This description is critically incomplete - it only specifies timing ('before writing implementation code') without ever explaining what the skill actually does. The vague scope ('any feature or bugfix') makes it indistinguishable from countless other development skills and provides no concrete actions or capabilities.
Suggestions
Add specific concrete actions describing what this skill does (e.g., 'Creates implementation plans', 'Analyzes requirements', 'Designs architecture', 'Writes test cases first')
Narrow the scope to a specific type of pre-implementation activity to reduce conflict with other skills (e.g., 'Generates TDD test specifications' or 'Creates technical design documents')
Include more natural trigger terms users would say, such as 'plan', 'design', 'architecture', 'before coding', 'preparation', or specific methodology terms
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only states when to use the skill ('before writing implementation code') but never describes what the skill actually does. 'Implementing any feature or bugfix' is extremely vague. | 1 / 3 |
Completeness | The description only addresses 'when' (before writing implementation code) but completely fails to explain 'what' the skill does. There is no indication of the skill's actual capabilities or actions. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'feature', 'bugfix', and 'implementation code' that users might naturally say, but lacks common variations like 'bug fix', 'new feature', 'coding', 'development', or specific task types. | 2 / 3 |
Distinctiveness Conflict Risk | 'Any feature or bugfix' is extremely broad and would conflict with virtually any development-related skill. There's nothing distinctive about this description to differentiate it from other coding or development skills. | 1 / 3 |
Total | 5 / 12 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.