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.
80
75%
Does it follow best practices?
Impact
Pending
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 strong skill description that clearly defines what the skill does (create user stories with specific frameworks and components) and when to use it (writing stories, breaking down features, defining acceptance criteria). It uses third person voice, includes natural trigger terms, and occupies a distinct niche with methodology-specific language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating user stories following the 3 C's and INVEST criteria, writing descriptions, design links, and acceptance criteria. These are well-defined, concrete deliverables. | 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'). | 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 domain-specific terminology like 'backlog items' and 'acceptance criteria' makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid template and example for user story creation, making the expected output format clear. However, it lacks depth in the actual decomposition process—how to identify the right story boundaries, validate INVEST compliance, and iterate on stories that don't meet criteria. The content is moderately concise but includes some redundancy and could be tightened.
Suggestions
Add concrete decision criteria or heuristics for decomposing features into stories (e.g., 'If a story requires more than X acceptance criteria, consider splitting it').
Include a validation/review step in the workflow, such as an INVEST checklist to verify each story against before finalizing output.
Remove or condense the 'Output Deliverables' section, as it largely restates what the template and example already demonstrate.
Add guidance on common pitfalls (e.g., stories that are too coupled, acceptance criteria that aren't testable) with brief examples of bad vs. good patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is 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 'Further Reading' link adds minimal value. | 2 / 3 |
Actionability | Provides a clear template and a good concrete example, but the guidance is more of a structured format than executable steps. The process steps (1-7) are somewhat vague ('Analyze the feature', 'Identify user roles') without concrete techniques or decision criteria for how to decompose features into stories. | 2 / 3 |
Workflow Clarity | The 7-step process provides a reasonable sequence, but lacks validation checkpoints. There's no guidance on how to verify story quality (e.g., checking INVEST compliance after drafting), no feedback loop for refining stories that are too large or dependent, and no explicit review step before finalizing output. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections (process, template, example, deliverables), but everything is inline in a single file. The template and example are appropriately concise, but the 'Further Reading' external link is weakly signaled and the content could benefit from separating advanced patterns (e.g., edge case handling, epic decomposition strategies) into a referenced file. | 2 / 3 |
Total | 8 / 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
36ccefd
- 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.