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.
66
78%
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 ./pm-execution/skills/user-stories/SKILL.mdQuality
Discovery
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.
This is a well-crafted skill description that clearly communicates what the skill does and when to use it. It uses specific methodologies (3 C's, INVEST) as distinguishing markers, includes natural trigger terms that product managers and developers would use, and has an explicit 'Use when' clause with multiple trigger scenarios.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating user stories following the 3 C's framework, applying INVEST criteria, writing descriptions, including design links, and defining acceptance criteria. | 3 / 3 |
Completeness | Clearly 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') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'user stories', 'backlog items', 'acceptance criteria', 'features', 'breaking down features'. These are terms commonly used by product managers and developers. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around user story creation with specific methodologies (3 C's, INVEST). The combination of these frameworks and product backlog terminology makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured skill for user story creation that provides a useful template and concrete example. Its main weaknesses are in actionability — the decomposition process is described at a high level without concrete decision-making guidance — and workflow clarity, which lacks validation steps to ensure story quality and INVEST compliance. The content could be tightened by removing redundant framing and adding more specific guidance on the decomposition process.
Suggestions
Add concrete guidance on how to decompose a feature into stories — e.g., 'identify distinct user interactions with the feature, each becomes a candidate story' with a worked example showing a feature broken into 3-4 stories.
Add a validation checkpoint after story generation: 'Review each story against INVEST — if a story isn't Independent, split it; if not Testable, rewrite acceptance criteria as observable behaviors.'
Remove the redundant opening paragraph that restates the description and the 'Output Deliverables' section which mostly repeats what's already implied by the template and process.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy — the opening paragraph restates the YAML description, and phrases like 'Use plain language a primary school graduate can understand' and the output deliverables section add moderate padding. The template and example are useful but the framing around them could be tighter. | 2 / 3 |
Actionability | The skill provides a clear template and a concrete example story, which is helpful. However, the step-by-step process is more of a checklist of principles than executable guidance — it tells Claude to 'analyze the feature' and 'identify user roles' without concrete techniques or decision criteria. The example is good but there's only one, and no guidance on how to decompose a feature into multiple stories. | 2 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. There's no guidance on how to verify story quality (e.g., checking INVEST criteria against each story, reviewing for overlap/gaps between stories). For a skill that involves breaking features into multiple stories, a review/validation step would be important. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~70 lines) with no bundle files, the content is well-organized with clear sections: process, template, example, and deliverables. The external link to further reading is appropriate. No need for additional file references given the scope. | 3 / 3 |
Total | 9 / 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
- phuryn/pm-skills
- Commit
d384f0c
- 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.