tdd-workflow

Test-Driven Development workflow for autonomous coding. Use when implementing features with TDD, writing tests first, following red-green-refactor, or ensuring test coverage.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/tdd-workflow/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

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

The body is a reasonably actionable overview with real backing scripts, but it is held back by decorative re-explanation of well-known TDD concepts, missing in-body validation checkpoints, and broken reference-file links. Tightening the diagram/tables and adding explicit feedback loops would materially improve it.

Suggestions

Replace the large ASCII cycle diagram and the 'TDD Principles' table with a terse phase list — Claude already knows red-green-refactor, so these tokens add little.

Add explicit validation/feedback checkpoints to the workflow, e.g. after RED ('confirm the test fails for the right reason') and after GREEN ('confirm all tests pass before refactoring'), with a fix-and-retry loop.

Create the missing references/TDD-BEST-PRACTICES.md and references/TEST-PATTERNS.md files (or remove the broken references) so the signaled navigation resolves.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the large ASCII TDD-cycle diagram and the 'TDD Principles' table restate red-green-refactor concepts Claude already knows, adding padding that could be trimmed.	3 / 5
Actionability	Quick Start provides executable Python calling a real TDDWorkflow class with phase methods, and the referenced scripts exist; minor gaps (undefined project_dir/criteria variables) keep it just below fully copy-paste ready.	4 / 5
Workflow Clarity	The RED→GREEN→REFACTOR→VERIFY sequence is shown, but the body lacks explicit validation/feedback-loop checkpoints (e.g., 'if tests fail, fix and re-run'); error recovery is only named via the error-recoverer integration point.	3 / 5
Progressive Disclosure	Sections are well organized and references are clearly signaled, but the two referenced files (references/TDD-BEST-PRACTICES.md, references/TEST-PATTERNS.md) do not exist, so navigation is broken for those paths.	3 / 5
	Total	13 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, explicit 'Use when...' trigger guidance with concrete natural phrases, and a clear TDD niche. It is comprehensive on the what/when axis with only minor specificity and synonym-coverage gaps.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('writing tests first', 'following red-green-refactor', 'ensuring test coverage'), though they describe TDD methodology rather than distinct capabilities, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Test-Driven Development workflow for autonomous coding') and when ('Use when implementing features with TDD, writing tests first, following red-green-refactor, or ensuring test coverage') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural terms a user would say ('TDD', 'writing tests first', 'red-green-refactor', 'test coverage'), with a few synonyms/variants missing.	4 / 5
Distinctiveness Conflict Risk	Clear TDD niche with distinct triggers ('red-green-refactor', 'writing tests first'), with minor overlap risk against general feature-implementation coding skills.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/tdd-workflow/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.