014-agile-user-story

Guides the creation of agile user stories. Use when the user wants to create a user story. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story; Split feature requirements into user stories. Part of Plinth Toolkit

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/014-agile-user-story/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

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 instruction skill with a clear workflow and explicit INVEST validation, supported by a properly linked one-level reference. Its main weakness is duplication between the Constraints and Workflow sections and between the body and the reference file.

Suggestions

Remove the duplicated constraints between the 'Constraints' section and the 'Workflow' step constraints (e.g., strict order, exact template wording, sanitized story facts) — state them once, ideally inside the workflow steps.

Drop or trim the 'When to use this skill' section in the body since the same trigger phrases already appear in the frontmatter description, freeing token budget.

Move the detailed INVEST/output checklist into the reference and keep only a one-line pointer in the body to avoid duplicating checklist content across the two files.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concept over-explanation, but the Constraints section and the Workflow step constraints duplicate 'strict order', 'exact wording from the template', and 'sanitized story facts', and the 'When to use' section repeats frontmatter triggers. Not 4 because the duplication is a clear tightening opportunity; not 2 because the body is short and largely lean.	3 / 5
Actionability	Concrete, specific constraints (one-by-one ordering, wait for response, sanitized-summary rule, INVEST pass/fail checkpoint) give mostly executable guidance; the question/Markdown templates live in the linked reference by design. Not 5 because the top-level workflow step labels ('Gather story details', 'Generate the user story artifact') are abstract without the reference; not 3 because the constraints add concrete, actionable specificity.	4 / 5
Workflow Clarity	A clear 3-step sequence with an explicit validation checkpoint ('INVEST pass/fail checkpoint with concrete evidence for each criterion before finalizing') and wait-for-response gating. Not 5 because the body's output checklist is brief ('Check output completeness') and the detailed checklist lives in the reference; not 3 because validation is explicitly present.	4 / 5
Progressive Disclosure	The body is a well-organized overview with clearly signaled one-level-deep navigation to a real file ([references/014-agile-user-story.md], verified present). Not 5 because some constraint content is duplicated between the body and the reference, a minor organization gap; not 3 because structure and signaling are clean and the reference is genuinely one level deep.	4 / 5
	Total	15 / 20 Passed

Description

78%Weight 40%Scale 1-5

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 that clearly states both capability and explicit trigger conditions with natural user phrasings. The main weakness is modest action breadth and the toolkit framing that hints at sibling-skill overlap.

Dimension	Reasoning	Score
Specificity	Names the domain ('agile user stories') plus two concrete actions ('Guides the creation' and 'Split feature requirements into user stories'), but the action set is not comprehensive. Not 4 because it does not list several specific distinct actions; not 2 because the actions named are concrete rather than purely generic.	3 / 5
Completeness	Explicitly answers both 'what' ('Guides the creation of agile user stories') and 'when' with concrete trigger phrases ('Use when the user wants to create a user story. This should trigger for requests such as...'). Matches the anchor-5 example closely; not lower because both halves are clearly and explicitly present.	5 / 5
Trigger Term Quality	Four natural trigger phrasings a user would actually say ('Create a user story; Write a user story; I need to write a user story; Split feature requirements into user stories') give good coverage. Not 5 because synonym breadth is limited (create/write variants only) and there are no further natural variations.	4 / 5
Distinctiveness Conflict Risk	'agile user stories' is a clear, distinct niche with minimal conflict risk, but the trailing 'Part of Plinth Toolkit' implies sibling skills that could create minor overlap. Not 5 because of that toolkit context; not 3 because the triggers are specific to user-story creation.	4 / 5
	Total	16 / 20 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/014-agile-user-story/SKILL.md
Commit: 77b8825

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