014-agile-user-story
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
74
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/014-agile-user-story/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its domain (agile user stories and BDD/Gherkin), lists specific actions, provides explicit trigger guidance with a 'Use when...' clause, and even includes example user phrases. The only minor weakness is the trailing 'Part of cursor-rules-java project' which adds little selection value, but overall the description is well-crafted for skill selection purposes.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: creation of agile user stories, Gherkin feature files, writing acceptance criteria, and defining Gherkin scenarios. These are distinct, concrete deliverables. | 3 / 3 |
Completeness | Clearly answers both 'what' (guides creation of agile user stories and Gherkin feature files) and 'when' (explicit 'Use when...' clause with multiple trigger conditions, plus example request phrases). Both dimensions are well-covered. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'user story', 'acceptance criteria', 'Gherkin scenarios', 'BDD feature files', and even provides example phrases like 'Create a user story', 'Write a user story', 'I need to write a user story'. Good coverage of natural language variations. | 3 / 3 |
Distinctiveness Conflict Risk | The skill occupies a clear niche around agile user stories, Gherkin/BDD feature files, and acceptance criteria. These are highly specific domain terms unlikely to conflict with other skills unless there's another BDD-specific skill. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill establishes a reasonable interactive workflow structure with clear constraints and a quality validation checkpoint (INVEST), but it critically lacks actionable content. Nearly all concrete guidance—example questions, template wording, output formats, Gherkin examples—is delegated to an external reference file that wasn't provided in the bundle. Without that reference, the skill body alone is insufficient for Claude to execute the task.
Suggestions
Add at least one concrete example of a completed user story Markdown output and a corresponding Gherkin .feature file so Claude knows the expected format without relying solely on the reference file.
Include 2-3 sample questions from the interactive questionnaire directly in the skill body so the workflow is actionable even if the reference file is unavailable.
Operationalize the INVEST validation step with specific pass/fail criteria and examples (e.g., 'Small: story can be completed in one sprint; FAIL if story contains multiple independent deliverables').
Provide the referenced bundle file (references/014-agile-user-story.md) or inline its key content to ensure the skill is self-sufficient.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary explanation like the 'What is covered in this Skill?' section which largely restates what's obvious from the workflow. The INVEST acronym expansion is helpful but the bullet list of coverage areas adds little value for Claude. | 2 / 3 |
Actionability | The skill provides no concrete examples of the user story template, no sample Gherkin output, no example questions to ask, and no file naming conventions. It entirely delegates to a reference file (references/014-agile-user-story.md) without providing any executable or copy-paste-ready content in the skill body itself. | 1 / 3 |
Workflow Clarity | The three workflow steps are clearly sequenced (gather → generate → validate), and the INVEST validation checkpoint is a good quality gate. However, the actual steps lack specificity—there are no concrete examples of what questions to ask, what the artifacts look like, or what constitutes pass/fail for each INVEST criterion. The validation step is mentioned but not operationalized. | 2 / 3 |
Progressive Disclosure | The skill references a single external file (references/014-agile-user-story.md) which is appropriate one-level-deep disclosure. However, the bundle files indicate no such file was provided, making it impossible to verify the reference exists. The skill body is too thin—it delegates almost everything to the reference without providing enough standalone content to be useful if the reference is unavailable. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%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
- jabrena/cursor-rules-java
- Commit
762cb86
- 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.