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
56
62%
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
89%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 solid skill description that clearly communicates its purpose and when to use it. It includes explicit trigger guidance with example phrases and covers relevant natural keywords. The main area for improvement is adding more specific concrete actions beyond the general 'guides the creation' framing, and the trailing 'Part of cursor-rules-java project' adds little value for skill selection.
Suggestions
Add more specific concrete actions such as 'generates Given/When/Then scenarios', 'structures stories with role-goal-benefit format', or 'creates feature file templates' to improve specificity.
Remove or relocate 'Part of cursor-rules-java project' as it doesn't help Claude select this skill and adds noise to the description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (agile user stories, Gherkin feature files) and mentions some actions (create user stories, write acceptance criteria, define Gherkin scenarios), but it doesn't list deeply specific concrete actions like template structures, formatting rules, or output details. | 2 / 3 |
Completeness | Clearly answers both 'what' (guides creation of agile user stories and Gherkin feature files) and 'when' (explicit 'Use when...' clause with specific trigger scenarios and example requests). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'user story', 'acceptance criteria', 'Gherkin scenarios', 'BDD feature files', and even example phrases like 'Create a user story', 'Write a user story'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of agile user stories, Gherkin, BDD, and acceptance criteria creates a clear niche that is unlikely to conflict with other skills. The domain is well-defined and distinct. | 3 / 3 |
Total | 11 / 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 defines a reasonable interactive workflow structure with clear sequencing and an INVEST validation checkpoint, but it critically lacks actionable content. Nearly all concrete guidance—question templates, output examples, Gherkin format specifics—is deferred to a reference file that wasn't provided, making the SKILL.md itself insufficient for Claude to execute the task. The content reads more like a process description than executable instructions.
Suggestions
Include at least one concrete example of a completed user story Markdown output and a corresponding Gherkin .feature file so Claude knows the exact target format.
Inline the key questionnaire questions (or at minimum a representative subset) directly in the SKILL.md rather than relying entirely on the external reference file for all actionable content.
Add specific INVEST validation criteria with concrete pass/fail examples (e.g., 'Small: story should be completable in one sprint; FAIL if story contains multiple independent features').
Provide a sample Gherkin scenario with Given/When/Then and data examples to make the expected output format unambiguous.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'What is covered in this Skill?' section, spelling out INVEST acronym) and could be tightened. The constraints section has some redundancy ('Use exact wording from the template' appears twice). However, it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides no concrete examples of user story output, no sample Gherkin feature file, no template of the questions to ask, and no executable guidance. It repeatedly references a template file for 'exact wording' but provides none of the actual content inline, leaving Claude with vague direction like 'Run the interactive questionnaire in strict order.' | 1 / 3 |
Workflow Clarity | The three-step workflow (gather, generate, validate) is clearly sequenced and includes an INVEST validation checkpoint, which is good. However, the steps lack specificity—there are no concrete examples of what the questionnaire looks like, what the output artifacts should contain, or what constitutes pass/fail for each INVEST criterion. The validation step is present but underspecified. | 2 / 3 |
Progressive Disclosure | The skill references a single external file (references/014-agile-user-story.md) for detailed guidance, which is appropriate one-level-deep disclosure. However, no bundle files were provided to verify the reference exists, and the SKILL.md itself is too thin—it delegates almost all actionable content to the reference file, leaving the main skill without enough standalone value. The 'What is covered' section acts as a table of contents but doesn't link to subsections. | 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
26e9744
- 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.