tdd-workflow

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

Quality

72%

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 ./.kiro/skills/tdd-workflow/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.

The body is highly actionable with a clearly sequenced, validated TDD workflow and executable code. Its main weakness is verbosity — it teaches generic testing concepts Claude already knows and is a monolithic file that could benefit from splitting detailed recipes into reference files.

Suggestions

Remove or condense generic material Claude already knows (the 'Best Practices' list, 'Test Types' definitions, 'Arrange-Act-Assert') to tighten token efficiency.

Move the detailed mocking recipes and per-runner test patterns into one-level-deep reference files (e.g., MOCKING.md, PATTERNS.md) linked from the overview.

Complete the stubbed test examples (e.g., '// Test implementation', '// Test error handling') so every example is fully executable.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with valuable concrete material (Step 0 runner detection, executable patterns), but it pads in concepts Claude already knows ('Unit Tests - Individual functions and utilities', the 10-item 'Best Practices' list, 'Arrange-Act-Assert') and could be tightened considerably.	2 / 3
Actionability	It provides fully executable, copy-paste-ready TypeScript and bash examples plus a concrete runner-command matrix; the '<test>'/'<coverage>' placeholders are explicitly resolved in Step 0, which is justified flexibility rather than pseudocode.	3 / 3
Workflow Clarity	The TDD Workflow is clearly sequenced (Step 0 through Step 7) with explicit validation gates — Step 3 'Run Tests (They Should Fail)' and Step 5 'Run Tests Again' form RED/GREEN checkpoints, and Step 7 verifies coverage.	3 / 3
Progressive Disclosure	No bundle files exist and all content lives in a single ~460-line file with well-organized sections, but material that should be split out (mocking recipes, the multiple test patterns) is inline rather than one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 well-formed with an explicit 'Use when' trigger and a clear statement of what it enforces, satisfying completeness. It is somewhat generic in its trigger terms and could be more distinctive and specific about its concrete actions.

Suggestions

Add more specific concrete actions (e.g., 'write failing tests first, implement to green, refactor') rather than high-level coding activities.

Include common natural trigger terms users would say, such as 'testing', 'write tests', 'test coverage', or 'TDD', to improve trigger coverage and distinctiveness.

Tighten the trigger to scope it to test-driven work specifically, reducing overlap with general coding skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('writing new features, fixing bugs, or refactoring code') and a concrete enforcement action ('Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests'), but the actions are high-level coding activities rather than the multiple specific concrete actions a level-3 anchor demands.	2 / 3
Completeness	It explicitly answers both 'what' ('Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests') and 'when' with an explicit 'Use this skill when...' trigger clause.	3 / 3
Trigger Term Quality	It includes relevant natural terms ('writing new features, fixing bugs, or refactoring code', 'E2E tests'), but misses common variations a user would naturally say such as plain 'testing', 'write tests', 'test coverage', or 'TDD'.	2 / 3
Distinctiveness Conflict Risk	The TDD/coverage framing gives it a niche, but the triggers ('writing new features, fixing bugs, or refactoring code') are generic coding activities that would overlap with many general development skills.	2 / 3
	Total	9 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/tdd-workflow/SKILL.md
Commit: 754b8dd

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.