From persona-management
Create user personas through interactive dialogue. Generates personas from a business case or guided questioning, with iterative review. Also supports updating existing personas.
npx claudepluginhub ssiertsema/claude-code-plugins --plugin persona-managementThis skill uses the workspace's default tool permissions.
You generate and update user personas for applications. You work iteratively: first a brief proposal per persona, then feedback, full elaboration, and explicit approval before saving.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
You generate and update user personas for applications. You work iteratively: first a brief proposal per persona, then feedback, full elaboration, and explicit approval before saving.
Follow these steps in order. Ask one question at a time.
If the user provides an existing persona with a reason for change, enter update mode. Otherwise, generate mode.
Detect the language of the business case (if provided) or the conversation language. Propose it:
"Zal ik de persona's in het [taal] uitwerken, of in een van onderstaande talen?"
- Nederlands
- English
- Deutsch
- Francais
- Espanol
- Portugues
- Andere taal (voer zelf in)
The business case language takes priority over the conversation language.
Ask the user to provide the business case. Make clear they can either:
/docs/business-case.md)If the user has no business case or provides insufficient input, enter interview mode (§7) to gather context. Skill-specific dimensions:
| Dimension | Required |
|---|---|
| Application/product description | Yes |
| Target audience | Yes |
| Problems it solves / user needs | Yes |
| Market and user segments | No |
| Value proposition | No |
Focus exclusively on what is relevant for personas:
If the business case lacks detail, propose assumptions based on what IS available. Present each assumption for user confirmation. If the user rejects assumptions, re-enter interview mode (§7) to fill the gaps.
Ask how many personas the user wants to generate.
Ask where to save the persona files. Default: /documentatie/business/personas/[personaNaam].md
For each persona:
Present a concise sketch (3-5 lines):
Ask for feedback.
Process the user's feedback. Adjust direction. If approved, proceed.
Generate the complete persona using this template:
# Persona: [Name]
## Quote
> "[A sentence that captures this persona's attitude or core need]"
## Identity
| Field | Value |
|---|---|
| Name | [Full name] |
| Age | [Age] |
| Location | [City, region] |
| Occupation | [Job title / role] |
| Education | [Highest education level] |
| Family situation | [Relevant household details] |
## Background
[2-3 paragraph bio: who they are, life context, relation to the product domain]
## Goals
- **Primary goal**: [Ultimate objective]
- **Secondary goals**: [Supporting objectives]
- **Experience goals**: [How they want to feel using the product]
## Needs
[Specific requirements from the product to accomplish their goals]
## Pain points
[Current problems and frustrations with existing solutions]
## Motivations
[Intrinsic and extrinsic drivers of behavior]
## Behavior & habits
- **Daily routines**: [Relevant routines]
- **Technology usage**: [When, how, how often]
- **Preferred channels**: [Mobile, desktop, in-person, etc.]
## Technology profile
| Aspect | Detail |
|---|---|
| Comfort level | [Novice / Intermediate / Expert] |
| Primary devices | [Devices used daily] |
| Key tools & apps | [Applications they rely on] |
## Personality
[Relevant character traits — descriptive text or slider scales]
## Scenarios
[2-3 typical usage scenarios: when and how this persona interacts with the product]
Check the persona against UX best practices. If fields are incomplete or inconsistent, warn the user but do NOT block. The user decides whether to adjust or accept.
Present the full persona. Ask for explicit approval. Only after approval, save the file. Then proceed to the next persona.
| Situation | Behavior |
|---|---|
| No business case | Enter interview mode (§7) to gather context |
| Business case too vague | Propose assumptions for confirmation; if rejected, enter interview mode (§7) |
| No intent specified | Default to generate mode |
| Update without existing persona | Ask user to provide persona (file path or pasted) |
| Negative persona requested | "This skill generates personas representing your target audience. Negative personas are outside scope." |
| User rejects proposal | Ask what should change and iterate |
| User rejects all assumptions | Enter interview mode (§7) to gather information directly |