User Personas

Extract persona candidates from project documentation and map them to task workflows.

6|3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/carson-sweet/sweetclaude --skill user-personas-carson-sweet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: User Personas
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/user-personas
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill user-personas-carson-sweet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of vague or disconnected user definitions by forcing a structured, evidence-based approach to persona creation that integrates directly into your product development lifecycle.

Core Features & Use Cases

  • Evidence-Based Definition: Extracts persona candidates from existing project documentation like PRDs and research notes to ensure grounding in reality.
  • Workflow Integration: Defines specific tasks, success criteria, and failure modes for each persona, ensuring that product features are built to solve actual user problems.
  • Lifecycle Management: Provides built-in state management to pause, resume, or offboard persona data, keeping your project state clean and organized.

Quick Start

Invoke the user personas skill to begin defining your target users and their primary goals by running the command /sweetclaude:user-personas onboard.

Frequently Asked Questions about User Personas

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

FAQPage Schema
How do I define user personas from existing product documentation?

Extract user persona candidates directly from existing project documentation like PRDs and research notes to ensure evidence-based definition. This grounds your personas in reality rather than assumptions, mapping them to specific task workflows.

What is the best way to map user requirements to product workflows?

Map user requirements to workflows by defining specific tasks, success criteria, and failure modes for each persona. This ensures product features are built to solve actual user problems and align with user needs throughout the product lifecycle.

How does persona state management work across the product lifecycle?

Persona state management tracks status, task definitions, and anti-profiles throughout the project lifecycle. It provides built-in controls to pause, resume, or offboard persona data, keeping your project state clean and organized.

Can I extract persona candidates from research notes and PRDs?

Yes, the skill extracts persona candidates from project documentation like PRDs and research notes. This evidence-based approach ensures your user definitions are grounded in actual project data rather than disconnected assumptions.

When do I need to define anti-profiles for product management?

Anti-profiles are needed when tracking persona status and task definitions across the project lifecycle to identify users you are explicitly not targeting. This prevents scope creep and ensures features remain aligned with intended user needs.

Why use structured user personas instead of generic user definitions?

Structured user personas solve the problem of vague or disconnected user definitions by forcing an evidence-based approach that integrates directly into your product development lifecycle. This ensures features align with actual user needs and success criteria.