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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

A well-structured interactive skill: clear sequenced workflow with a validation checkpoint and a clean one-level reference split. The main weaknesses are repetition between the Constraints and Workflow sections and the deferral of the actual templates/question wording to the reference.

Suggestions

Dedupe the MUST items shared between the 'Constraints' section and the 'Workflow' step constraints — state each rule once and reference it, to tighten conciseness.

Inline the user-story Markdown and Gherkin output templates (or at least a compact skeleton) in the body so the skill is actionable without opening the reference, rather than only saying 'use exact wording from the referenced template'.

Drop the 'When to use this skill' list since those triggers already appear verbatim in the frontmatter description, removing redundant tokens.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concept exposition, but the Constraints and Workflow step-constraints repeat the same MUST items (one-by-one questioning, exact wording, wait-for-response, sanitized facts, repeat scenarios, INVEST), and the 'When to use' section re-lists triggers already in the description — it could be tightened.	2 / 3
Actionability	The workflow and constraints are concrete, but the genuinely copy-paste-ready detail (exact question wording, the user-story and Gherkin output templates) is deferred to the reference rather than present in the body, leaving the body's own guidance incomplete per the score-2 anchor.	2 / 3
Workflow Clarity	A clear three-step sequence (Gather → Generate → Validate) with an explicit INVEST pass/fail checkpoint 'with concrete evidence for each criterion before finalizing', matching the score-3 anchor for sequenced steps with validation.	3 / 3
Progressive Disclosure	The body is a concise overview that points to a single, well-signaled one-level-deep reference ('see references/014-agile-user-story.md'), and that referenced file exists, fitting the score-3 anchor.	3 / 3
	Total	10 / 12 Passed

Description

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.

A strong, specific description with explicit capability listing and a clear 'Use when' trigger clause using natural user phrasings. The distinct BDD/Gherkin niche keeps conflict risk low.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files' — matching the score-3 anchor rather than the partial coverage of score 2.	3 / 3
Completeness	Explicitly answers both what ('Guides the creation of agile user stories and Gherkin feature files') and when ('Use when the user wants to...'), with an explicit trigger clause, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	Includes natural phrasings a user would actually say ('Create a user story; Write a user story; I need to write a user story') plus 'Use when' guidance, giving good coverage rather than the sparse keyword set of score 2.	3 / 3
Distinctiveness Conflict Risk	The agile user story + Gherkin/BDD feature-file niche has distinct triggers unlikely to collide with other skills, fitting the score-3 'clear niche' anchor.	3 / 3
	Total	12 / 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/cursor-rules-java
Commit: 86eb63d

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