058-design-bdd

Use when a Java change needs independent Behavior-Driven Development guidance from trusted behavior facts through concrete examples and observable scenarios, with focused clarification when behavior is pending or ambiguous. This should trigger for requests such as Apply BDD; Facilitate behavior examples; Discover scenarios with Given When Then; Review these examples for shared domain language; Complete BDD discovery as a self-contained interaction. Part of Plinth Toolkit

Quality

85%

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

Quality

Content

85%

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

A well-structured, actionable instruction-only skill with a clear sequenced workflow and clean one-level progressive disclosure to a single bundled reference. The main weakness is redundancy: the reference path and several example/language points are restated across multiple sections and could be consolidated.

Suggestions

Consolidate the six repeated mentions of `references/058-design-bdd.md` into the 'Reference' section and a single constraint, removing duplicates from 'What is covered' and the workflow steps.

Merge overlapping content between 'What is covered in this Skill?' and the 'Workflow'/'Constraints' sections so each example-type and shared-language point appears once.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and avoids explaining concepts Claude already knows, but it repeats `references/058-design-bdd.md` six times and restates the same example types (main/alternative/boundary/error) and shared-language/Given-When-Then points across the 'What is covered', 'Constraints', and 'Workflow' sections, so it could be tightened.	2 / 3
Actionability	For an instruction-only design skill, the guidance is concrete and actionable: it names specific deliverables (actors, outcomes, business rules, terminology, main/alternative/boundary/error examples) and explicit steps (read the reference, confirm facts, formulate Given/When/Then scenarios, report unresolved items), so absence of code is not penalized per the rubric scoring notes.	3 / 3
Workflow Clarity	The four-step workflow is clearly sequenced with gating and feedback checkpoints — confirm actors/rules 'before formulating scenarios', ask focused follow-ups when facts are ambiguous, and report unresolved decisions/conflicts/risks in step 4.	3 / 3
Progressive Disclosure	The body is an overview that points to a single one-level-deep bundle file, `references/058-design-bdd.md` (verified to exist), signaled via a dedicated 'Reference' section, with no nested reference chains.	3 / 3
	Total	11 / 12 Passed

Description

85%

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

A strong, explicit description that clearly answers both 'what' and 'when' and is scoped to a distinct BDD/Java niche. Its main weakness is trigger phrasing: several listed triggers read as internal/formal labels rather than words a user would naturally say.

Suggestions

Rewrite stilted triggers ('Facilitate behavior examples', 'Complete BDD discovery as a self-contained interaction') into natural user phrasing such as 'Help me write behavior examples' or 'Run BDD discovery for this change'.

Add common BDD variations users actually say (e.g., 'write Gherkin scenarios', 'turn requirements into Given/When/Then') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the Java/BDD domain and lists multiple concrete actions — 'guidance from trusted behavior facts through concrete examples and observable scenarios', 'focused clarification', plus a trigger list including 'Apply BDD', 'Discover scenarios with Given When Then', and 'Complete BDD discovery'.	3 / 3
Completeness	It explicitly states what the skill does ('independent Behavior-Driven Development guidance from trusted behavior facts...') and when to use it via an explicit 'Use when...' clause and 'This should trigger for requests such as...'.	3 / 3
Trigger Term Quality	It includes some natural phrases a user would say ('Apply BDD', 'Discover scenarios with Given When Then'), but several triggers are stilted/corporate rather than user-natural ('Facilitate behavior examples', 'Complete BDD discovery as a self-contained interaction'), missing common variations.	2 / 3
Distinctiveness Conflict Risk	It is scoped to a clear niche — Java changes needing BDD guidance as a self-contained interaction — with distinct BDD-specific triggers, making conflict with unrelated skills unlikely.	3 / 3
	Total	11 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/058-design-bdd/SKILL.md
Commit: 26b0e71

Reviewed: about 21 hours 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.