skills.rest
inho-team
inho-teamOFFICIAL
Explore all skills by this author →
GitHub

Qpm-user-story

Translate user needs into INVEST-form user stories with Gherkin acceptance criteria.

6|Updated Mar 14, 2026
Search Tags:#invest#gherkin#product-management#acceptance-criteria#user-story#story-writing
One-click install
npx skills add https://github.com/inho-team/qe-framework --skill qpm-user-story
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Qpm-user-story
Source: https://github.com/inho-team/qe-framework/tree/main/skills/Qpm-user-story
Command: npx skills add https://github.com/inho-team/qe-framework --skill qpm-user-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates clear, testable development tasks by converting user needs into Mike Cohn-style user stories paired with Gherkin acceptance criteria, ensuring INVEST alignment.

Core Features & Use Cases

  • Use Case format: As a [role], I want to [action], so that [outcome].
  • Acceptance Criteria: Scenarios written in Gherkin with Given/When/Then structure, ensuring testability.
  • INVEST validation: Built-in checks to ensure independence, negotiability, value, estimability, small size, and testability.
  • Workflow guidance: Step-by-step workflow to gather context, write, validate, and refine stories.

Quick Start

Provide a user need and desired outcome, and the tool will generate a complete INVEST-compliant user story with acceptance criteria.

Frequently Asked Questions about Qpm-user-story

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

FAQPage Schema
How do I write user stories with Gherkin acceptance criteria and INVEST validation?▼

To write user stories with Gherkin acceptance criteria and INVEST validation, provide a user need and desired outcome to generate Mike Cohn-style stories paired with Given/When/Then scenarios and a formal INVEST compliance checklist.

What is the INVEST principle for user story writing in product management?▼

The INVEST principle for user story writing ensures stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable, providing a validation checklist to guide QA and development for sprint planning.

Can I use Gherkin scenarios for sprint planning and backlog refinement?▼

Yes, you can use Gherkin scenarios for sprint planning and backlog refinement. They provide testable Given/When/Then acceptance criteria that ensure generated user stories are estimable and ready for development.

What is the best way to translate product discovery needs into testable development tasks?▼

The best way to translate product discovery needs into testable development tasks is converting them into Mike Cohn use case formats paired with Gherkin acceptance scenarios, ensuring clear requirements through structured INVEST validation.

When should I not use Mike Cohn style user stories for requirements?▼

You should not use Mike Cohn style user stories when requirements demand strict technical specifications rather than value-driven outcomes, as this format prioritizes negotiable, testable scenarios over rigid, exhaustive system documentation.

Related Skills

Explore More Product & Management Skills→
OsirsOsirs

job-stories

Generate Job Stories from user requirements using the Jobs-to-be-Done framework.

Community
Basic
QuestNova502QuestNova502
4

agile-product-owner

Generate INVEST-compliant user stories and sprint plans from epics.

Community
Advanced
warpcodewarpcode
2

pm-task-writer

Translate epics into user stories and Gherkin acceptance criteria.

Community
Intermediate
Z1-TestZ1-Test

feature-specification

Create feature specifications in Gherkin syntax within Markdown format.

Official
Intermediate