user-story-quality-coach

Analyze user stories with Jobs-to-be-Done theory and score six quality dimensions.

25|5|Updated May 1, 2026
One-click install
npx skills add https://github.com/josemerca/mercadona-user-story-toolkit --skill user-story-quality-coach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story-quality-coach
Source: https://github.com/josemerca/mercadona-user-story-toolkit/tree/main/skills/user-story-quality-coach
Command: npx skills add https://github.com/josemerca/mercadona-user-story-toolkit --skill user-story-quality-coach

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies issues in user stories, using the JTBD (Jobs-to-be-Done) framework and "50 Quick Ideas to Improve Your User Stories". It generates reports with scoring in 6 dimensions and detects anti-patterns.

Core Features & Use Cases

  • Story Analysis: Evaluates user stories for quality and completeness.
  • Scoring & Reports: Provides scoring on 6 dimensions and highlights anti-patterns.
  • Use Case: When reviewing sprint content, analyzing the backlog, or refining stories.

Quick Start

Analyze user stories with '/validate-stories <paste>'.

Frequently Asked Questions about user-story-quality-coach

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a user story for quality and anti-patterns?

You can analyze a user story for quality by pasting its content into the command line interface. The tool evaluates the story using the JTBD framework and provides a score across six dimensions while detecting anti-patterns.

What is the JTBD framework for story refinement?

The JTBD framework for story refinement evaluates user stories based on the Jobs-to-be-Done theory. It identifies functional and emotional needs to ensure stories deliver value, generating reports with quick improvement ideas for sprint reviews and backlog analysis.

How do I validate my backlog during a sprint review?

You validate your backlog during a sprint review by running the story analysis command with your pasted story content. It assesses completeness and highlights anti-patterns using established JTBD theory and quick improvement ideas.

Does story analysis require any external dependencies or APIs?

Story analysis does not require external dependencies or APIs. The tool operates entirely through manual user input in the CLI, processing story content locally to generate quality scores and improvement reports.

What are the limitations of CLI-based story analysis?

The limitation of CLI-based story analysis is that it requires manual user input for additional story information. It handles story content strictly through the command line, meaning there is no automated integration with external backlog management platforms.

Can I evaluate user stories for completeness without manual input?

Evaluating user stories for completeness requires manual input via the CLI. You must paste the story content into the command interface to trigger the analysis and receive the six-dimension scoring report.