tdd-cycle

Start a new TDD feature cycle for wheel-of-meeting. Guides strictly through Gherkin → failing test → implement → green suite.

Quality

71%

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 ./.claude/skills/tdd-cycle/SKILL.md

Quality

Content

88%Scale 1-5

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, well-structured TDD workflow skill. It is concise, assumes Claude's competence, and provides a clear 10-step sequence with multiple validation checkpoints and explicit stop-and-report gates. The main area for improvement is that implementation guidance in step 7, while specific to the project's architecture, could benefit from a brief code snippet showing the pattern.

Dimension	Reasoning	Score
Conciseness	Every line is actionable instruction. No unnecessary explanations of TDD concepts, Gherkin, or Playwright — it assumes Claude knows these. The entire skill is under 25 lines and every token earns its place.	5 / 5
Actionability	Provides specific file paths, commands (`npm test`, `npm run check`), and concrete patterns (where to place pure functions, how to use StateManager). However, it lacks executable code examples — the implementation guidance in step 7 is directional rather than copy-paste ready, which is appropriate for a workflow skill but prevents a 5.	4 / 5
Workflow Clarity	Excellent sequencing with explicit validation checkpoints: verify green suite before starting (step 2), stop for user approval (step 4), confirm new test fails (step 6), confirm all tests pass (step 8), run lint/format/audit (step 9). Includes feedback loops — if tests fail unexpectedly or pass when they shouldn't, the workflow stops and reports to the user.	5 / 5
Progressive Disclosure	References external files appropriately (tests/CLAUDE.md, src/CLAUDE.md, existing .feature files as style references) without inlining their content. However, no bundle files are provided to verify these references exist, and the references could be slightly more clearly signaled (e.g., with markdown links). For a skill under 25 lines, the structure is well-organized.	4 / 5
	Total	18 / 20 Passed

Description

53%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 communicates a clear workflow (Gherkin → failing test → implement → green) for a specific project, which aids distinctiveness. However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms and more specific action descriptions. The concise format is good but leaves gaps in completeness and trigger coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to add a new feature to wheel-of-meeting using TDD, or mentions writing tests, adding Gherkin scenarios, or starting a red-green-refactor cycle.'

Expand trigger terms to include synonyms and natural phrases like 'new feature', 'test-driven development', 'BDD', 'red-green-refactor', 'add scenario', or 'feature file'.

List more specific actions, e.g., 'Generates Gherkin feature files, writes failing test cases, implements production code, and verifies the full test suite passes.'

Dimension	Reasoning	Score
Specificity	Names the domain (TDD feature cycle for wheel-of-meeting) and describes a concrete workflow (Gherkin → failing test → implement → green suite), but doesn't list specific actions like 'generates Gherkin scenarios', 'creates test files', or 'runs test suite'.	3 / 5
Completeness	The 'what' is reasonably clear (guides through a TDD cycle with Gherkin → failing test → implement → green suite), but there is no explicit 'when' clause. The phrase 'Start a new TDD feature cycle' weakly implies when, but lacks a 'Use when...' trigger guidance.	3 / 5
Trigger Term Quality	Includes relevant terms like 'TDD', 'Gherkin', 'failing test', 'green suite', and the project name 'wheel-of-meeting', but misses natural user phrases like 'new feature', 'test-driven', 'BDD', 'red-green-refactor', or 'add feature'.	3 / 5
Distinctiveness Conflict Risk	The combination of the specific project name 'wheel-of-meeting' and the specific methodology (TDD with Gherkin) makes this fairly distinct. Minor overlap risk with generic TDD or testing skills, but the project scoping reduces conflict significantly.	4 / 5
	Total	13 / 20 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: koenighotze/wheel-of-meeting
Path: .claude/skills/tdd-cycle/SKILL.md
Commit: 18189d1

Reviewed: 6 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.