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 covering multiple scenarios. The description is concise yet comprehensive.
| 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 instruction-only skill with a good example and clear template. Its main weaknesses are the lack of validation/feedback loops in the workflow (e.g., checking stories against INVEST after drafting) and some redundancy between sections. The actionability could be improved with more specific guidance on how to decompose features and handle edge cases like overly large stories.
Suggestions
Add a validation step after story creation (e.g., 'Review each story against INVEST criteria: if a story isn't Independent or Small enough, split it further') to improve workflow clarity.
Remove the redundant 'Output Deliverables' section—its content is already conveyed by the template and example, and this would improve conciseness.
Make the step-by-step process more actionable by specifying concrete heuristics, e.g., 'Split by user role first, then by distinct UI interaction or API endpoint' rather than just 'Identify user roles.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary explanation. The 3 C's and INVEST criteria definitions are somewhat redundant for Claude, and the 'Output Deliverables' section restates what's already implied by the template and example. The 'Use when' line and description overlap with the opening paragraph. | 2 / 3 |
Actionability | Provides a clear template and a concrete example story, which is helpful. However, the guidance is more of a framework description than executable instructions—there's no concrete code or command, and the step-by-step process is somewhat abstract (e.g., 'Analyze the feature,' 'Identify user roles') without specifying how to do these things in practice. | 2 / 3 |
Workflow Clarity | Steps are listed in a logical sequence, but there are no validation checkpoints or feedback loops. For instance, there's no step to verify stories meet INVEST criteria after drafting, no review/refinement step, and no guidance on what to do if a story is too large or not independent. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope, the content is well-organized with clear sections (process, template, example, deliverables) and a single external reference link. No unnecessary nesting or monolithic walls of text. The structure is easy to navigate. | 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
020ee82
- 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.