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; Create Gherkin scenarios for a user story; Split feature requirements into user stories. Part of Plinth Toolkit

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.

The skill is a well-structured interactive workflow with clear sequencing and an explicit validation checkpoint, and it uses progressive disclosure cleanly with a real, single-level reference. Its weak spots are mild redundancy between the Constraints and Workflow sections and actionability that defers most concrete specifics to the reference file.

Suggestions

Remove the overlap between 'Constraints' and Workflow step 1 — state the strict-order and sanitized-facts rules once, then have the workflow reference them, to tighten conciseness.

Inline a minimal concrete artifact skeleton (a short user-story Markdown template and one Given/When/Then example) so the body is actionable without first opening the reference.

Drop or condense the 'When to use this skill' list since the same triggers already appear in the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but the Constraints section and Workflow step 1 overlap ('strict order', 'sanitized story facts', 'repeat scenario questions') and the 'When to use this skill' list duplicates triggers already in the description. It is not a 3 because this redundancy could be tightened; not a 1 because there is no padded concept explanation.	2 / 3
Actionability	Guidance names the two artifacts and lists INVEST criteria, but the concrete specifics — the actual questionnaire wording and output templates — live in the referenced file ('use exact wording from the template', 'see references/014-agile-user-story.md'), leaving key details inline-incomplete. It is not a 3 because nothing is copy-paste ready in the body; not a 1 because it does give concrete instructional guidance rather than vague direction.	2 / 3
Workflow Clarity	The workflow is clearly sequenced (gather, generate, validate) with an explicit INVEST pass/fail checkpoint 'before finalizing' and per-question wait gates. It is not a 2 because validation checkpoints are explicit rather than implicit or missing.	3 / 3
Progressive Disclosure	The body is a concise overview pointing to a single one-level-deep reference (references/014-agile-user-story.md), which exists in the bundle and is clearly signaled with a markdown link. It is not a 2 because content is appropriately split rather than inlined and navigation is straightforward.	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 description: it states concrete capabilities, provides explicit 'Use when' triggers with natural user phrasings, answers both what and when, and occupies a distinct niche. It uses correct third-person voice.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'create a user story', 'write acceptance criteria', 'define Gherkin scenarios', 'author BDD feature files' — matching the anchor for listing several specific concrete actions. It is not a 2 because it goes beyond naming just the domain and a few actions into a comprehensive set of capabilities.	3 / 3
Completeness	It answers both 'what' ('Guides the creation of agile user stories and Gherkin feature files') and 'when' with an explicit 'Use when...' clause listing triggers. It is not a 2 because the trigger guidance is explicit rather than implied.	3 / 3
Trigger Term Quality	It enumerates natural phrasings a user would actually say — 'Create a user story; Write a user story; I need to write a user story; Create Gherkin scenarios for a user story; Split feature requirements into user stories' — giving good coverage of common variations. It is not a 2 because it includes multiple natural phrasings rather than only a few relevant keywords.	3 / 3
Distinctiveness Conflict Risk	The niche (agile user stories and Gherkin/BDD feature files) is specific with distinct triggers unlikely to collide with other skills. It is not a 2 because the triggers are narrowly scoped to user-story/BDD authoring rather than broadly overlapping with general writing or documentation skills.	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/plinth
Commit: aaee915

Reviewed: 1 day 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.