skills.rest
Kwondongkyun
KwondongkyunCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pm-user-flow

Define user stories, flows, and edge cases with Given-When-Then acceptance criteria.

Updated Aug 23, 2026
Search Tags:#edge-cases#product-management#acceptance-criteria#user-flow#user-story#flow-mapping#invest-principles
One-click install
npx skills add https://github.com/Kwondongkyun/claude-code-settings --skill pm-user-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-user-flow
Source: https://github.com/Kwondongkyun/claude-code-settings/tree/main/skills/pm-user-flow
Command: npx skills add https://github.com/Kwondongkyun/claude-code-settings --skill pm-user-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams write clear, testable requirements by defining user stories, mapping end-to-end flows, and surfacing scenarios and edge cases for new features or screens.

Core Features & Use Cases

  • Standardized user-story templates with Given-When-Then acceptance criteria
  • User-flow mapping sections for primary, alternative, and error flows
  • Scenario & edge-case coverage checklists (data, network, device, user actions)
  • INVEST principle guidance (Independent, Negotiable, Valuable, Estimable, Small, Testable)
  • Templates for flow diagrams, scenarios, and edge-cases to streamline discovery

Quick Start

Draft a new pm-user-flow by listing the user type, goal, and acceptance criteria in Given-When-Then format, then map the primary flow.

Frequently Asked Questions about pm-user-flow

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

FAQPage Schema
How do I write user stories with acceptance criteria using Given-When-Then format?▼

User stories with acceptance criteria are defined using standardized Given-When-Then templates. This approach ensures clear, testable product requirements by mapping user types, goals, and specific conditions directly into structured scenarios for feature discovery and grooming.

What is the best way to map user flows and identify edge cases for new features?▼

Mapping user flows involves detailing primary, alternative, and error paths. Edge cases are identified using coverage checklists across data, network, device, and user actions, ensuring comprehensive scenario planning for web and mobile UX design.

How does INVEST principles evaluation work for product management requirements?▼

INVEST principles evaluate requirements by checking if they are Independent, Negotiable, Valuable, Estimable, Small, and Testable. This evaluation refines user stories during requirements grooming to ensure they are appropriately scoped and actionable.

Can I use this user flow mapping approach for both web and mobile platforms?▼

Yes, user flow mapping and edge-case scenario coverage apply directly to both web and mobile platforms. The structured templates support feature discovery and UX planning across diverse devices and network conditions without platform-specific limitations.

What should be included in edge case coverage checklists for user stories?▼

Edge case coverage checklists should include scenarios for data anomalies, network failures, device-specific constraints, and unexpected user actions. These checklists surface hidden scenarios during requirements grooming to prevent downstream development issues.

Related Skills

Explore More Product & Management Skills→
cna-bootcampcna-bootcamp
23

customer-analysis

Define target customer types using the Jobs To Be Done framework.

Official
Intermediate
sicktasticsicktastic

user-story

Create Mike Cohn user stories with Gherkin acceptance criteria.

Community
Intermediate
xmx0632xmx0632
1

product-design

okay, I'll respond with:

Community
Advanced
heaptracetechnologyheaptracetechnology
13

user-story

Convert vague feature requirements into structured user stories with acceptance criteria.

Community
Advanced