CtrlK
BlogDocsLog inGet started
Tessl Logo

user-stories

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.

65

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

The body is concise, well-structured, and actionable via a template plus worked example. Its main weakness is workflow clarity — the steps lack explicit validation or quality checkpoints before producing stories.

Suggestions

Add an explicit validation/review checkpoint (e.g., 'verify each story satisfies INVEST and has 4-6 testable acceptance criteria before finalizing') to the step-by-step process.

Tighten redundancy: the 3 C's and INVEST criteria are restated across the description, step list, and deliverables — consolidate to one place.

Clarify the output format contract (e.g., markdown schema or per-story block) so generation is copy-paste ready rather than implied by the example.

DimensionReasoningScore

Conciseness

Lean, sectioned content (steps, template, example) with little explanation of concepts Claude already knows; minor redundancy between the step list and the 3 C's/INVEST restatements keeps it off 5.

4 / 5

Actionability

A concrete story template and a worked acceptance-criteria example give mostly executable guidance; it stops short of fully copy-paste-ready output specs for all common cases.

4 / 5

Workflow Clarity

The 7-step process is sequenced but has no validation or feedback checkpoints; though this is non-destructive authoring, the sequence lacks explicit quality gates.

3 / 5

Progressive Disclosure

Well-organized sections with a single one-level-deep external link; no bundle files exist to split further, and the body slightly exceeds the 50-line simple-skill threshold.

4 / 5

Total

15

/

20

Passed

Description

87%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, third-person description that states concrete capabilities and an explicit 'Use when' trigger clause with natural phrasing. It is comprehensive and distinctive with only minor synonym gaps.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'create user stories', 'descriptions, design links, and acceptance criteria' — anchored in the 3 C's and INVEST frameworks, with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('Create user stories following the 3 C's ... and INVEST criteria with descriptions, design links, and acceptance criteria') and when ('Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria').

5 / 5

Trigger Term Quality

Natural phrases like 'writing user stories, breaking down features into backlog items, or defining acceptance criteria' match what users would say; a few synonyms (e.g., 'agile', 'epics') are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear agile/user-story niche with distinct triggers (3 C's, INVEST, backlog items) that are unlikely to fire for unrelated skills.

5 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
phuryn/pm-skills
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.