Results for “user-motivation”
8 skillsMore results
user-segmentation
Analyze diverse user feedback to identify at least 3 distinct behavioral and needs-based user segments based on jobs-to-be-done, behaviors, and motivations.
22.6k
persona
Generate data-driven user personas for UX research and product design. Usage: /persona generate [options]
0
diary-study-plan
Design a diary study plan with prompts, duration, participant criteria, and analysis framework to understand user behavior over time in natural contexts.
1.7k
user-personas
Create detailed, actionable user personas from research data, capturing jobs-to-be-done, pain points, desired gains, and unexpected behavioral insights to guide product decisions.
22.6k
user-personas
Creates research-backed user personas with JTBD, pain points, gains, and unexpected behavioral insights. Use when building personas from survey or interview data, or segmenting users to inform product decisions. Triggers on: user persona, user profile, customer segment, jobs-to-be-done, JTBD, persona creation, user segmentation, target user, who are our users.
3
user-persona
Create refined user personas from research data with demographics, goals, frustrations, and behavioral patterns for product and UX design decisions.
1.7k
jobs-to-be-done
Use to CREATE or REVIEW a Job to be Done (JTBD) in Alan Klement's demand-side, progress-based sense — a job is the progress a customer is trying to make, never a task or feature. Trigger whenever someone wants to write or draft a JTBD, job statement, or job story; figure out the real motivation, struggle, or progress behind a feature, request, or product; understand why customers switch, adopt, or churn; turn interview notes or research into jobs; or pressure-test, sharpen, or rewrite existing JTBDs into proper jobs. Also trigger on "grill my JTBD", "is this a real job or just a task/feature", "what's the actual job here", "why would they switch". In an A-Team target repo, jobs are durable artifacts — this skill writes docs/product/jtbd/NN-<slug>.md per CONTRACT.md and never deletes or silently rewrites a job. Do NOT use for writing PRDs, roadmaps, tickets, or acceptance criteria (those consume a finished JTBD), or for implementation user stories.
0 · bundle