skills.rest
shafibabar
shafibabarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

user-persona

Synthesize interview notes into evidence-based user personas grounded in past behaviors.

1|Updated Jun 20, 2026
Search Tags:#requirements#discovery#strategy#persona#user-research#jtbd
One-click install
npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill user-persona-shafibabar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-persona
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/user-persona
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill user-persona-shafibabar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of abstract, non-actionable requirements by anchoring product discovery in concrete, evidence-based user archetypes that drive design decisions.

Core Features & Use Cases

  • Proto vs Research Distinction: Enforces the honesty rule by requiring clear labeling of assumption-based personas versus those validated by real user interviews.
  • Evidence-Based Grounding: Provides a framework to map every persona attribute to specific past behaviors, ensuring requirements are load-bearing and not based on demographic decoration.
  • Strategic Integration: Connects personas directly to Jobs-to-be-Done (JTBD) analysis and user story writing to ensure every feature has a human anchor.

Quick Start

Use the user-persona skill to draft a research-grounded persona for the Data Steward role based on the provided interview notes.

Frequently Asked Questions about user-persona

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

FAQPage Schema
How do I create evidence-based user personas from interview notes?▼

To create evidence-based user personas, synthesize user goals, behaviors, and pain points into actionable archetypes by mapping every attribute to specific past user behaviors observed during interviews.

What is the difference between proto personas and research personas?▼

Proto personas are built on assumptions, while research personas are validated by real user interviews. This distinction enforces an honesty rule so teams avoid treating untested assumptions as factual user needs.

How do I ground product requirements in Jobs-to-be-Done analysis?▼

Ground product requirements in Jobs-to-be-Done analysis by connecting user personas directly to JTBD frameworks, ensuring every feature has a human anchor tied to specific past user behaviors.

How do I validate user persona attributes using the Mom-Test standard?▼

Validate user persona attributes using the Mom-Test standard by ensuring every characteristic is backed by specific past user behaviors rather than projections, ensuring requirements are load-bearing.

When should I use assumption-based personas during product discovery?▼

Assumption-based personas should only be used during early product discovery phases when real interviews are unavailable, and must be clearly labeled as proto personas to avoid misleading design decisions.

Why are abstract user requirements problematic for product strategy?▼

Abstract user requirements are problematic because they lack concrete behavioral anchors, leading to non-actionable design decisions that fail to address real user pain points and goals.

Related Skills

Explore More Product & Management Skills→
pisithrpspisithrps

user-research-synthesis

Extract quotes, behaviors, pain points, and workarounds from user interview transcripts.

Community
Advanced
courtneyr-devcourtneyr-dev
6

Product Management for WordPress

Create personas, user stories, and feature hypotheses for WordPress plugin development.

Community
Basic
yknothingyknothing
1

user-research

Generate a research plan, user personas, and journey map from user evidence.

Community
Advanced
argenargen
1

proto-persona

Create structured four-quadrant proto-personas from minimal input.

Community
Basic