persona-generation

Generates detailed user persona profiles from product briefs and market context.

Updated Aug 4, 2026
One-click install
npx skills add https://github.com/rombel00/game-processes --skill persona-generation-rombel00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: persona-generation
Source: https://github.com/rombel00/game-processes/tree/main/plugins/product-discovery/skills/persona-generation
Command: npx skills add https://github.com/rombel00/game-processes --skill persona-generation-rombel00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often work with a vague notion of a "target audience" that cannot be used to validate design or product decisions. This Skill turns an abstract audience into concrete, named personas with goals, ranked pains, current solutions, objections, and success criteria, so every loop-design or feature decision can be checked against a specific player profile. ## Core Features & Use Cases - Typed persona set: Produces primary, secondary, anti-persona, and early adopter profiles, scaled to product size (MVP, mid-size, enterprise). - Structured persona template: Each profile includes demographics, goals, pains ranked by severity, current solutions, buying behavior, objections, success criteria, and hypotheses to verify. - Interactive and pipeline modes: Runs as a guided interview with draft checkpoints saved to disk, or autonomously from a brief artifact with assumptions explicitly marked. - Use Case: Given a game brief describing a target audience of casual mobile players, generate one primary persona, one early adopter, and one anti-persona, then hand the personas file to the game-loop design or persona interview step. ## Quick Start Generate player personas from the current game brief, including a primary persona, an early adopter, and an anti-persona, and save them to the personas artifact path.

Frequently Asked Questions about persona-generation

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

FAQPage Schema
How do I create user personas from a product brief?▼

Provide the brief artifact as input and the skill extracts the audience, problem, and user constraints, then drafts a persona set covering primary, early adopter, and anti-persona types. Each persona follows a fixed template with goals, ranked pains, current solutions, objections, and success criteria.

What types of personas should a product team define?▼

Define at least one primary persona that drives design decisions, one early adopter who tolerates rough edges, and one anti-persona that clarifies who the product is not for. Secondary personas are optional and must not conflict with the primary.

Can persona generation run without user interaction in a pipeline?▼

Yes, in autonomous mode it reads the brief and optional market artifact, builds at least one primary and one early adopter persona, marks unproven claims as assumptions, writes the personas file, and returns a JSON envelope with status and artifact paths.

How many personas should I create for an MVP?▼

For an MVP or early-stage product, create one to two primary personas, zero to one secondary, one anti-persona, and one early adopter. The guiding rule is that two deep personas are more useful than five shallow ones.

What are the limitations of generated personas?▼

Personas are working hypotheses about users, not verified facts. Anything not grounded in the brief or market data is marked as an assumption or hypothesis, and profiles should be updated after real customer interviews and usage data.