From product
Generates Jobs-to-be-Done–anchored personas with job stories and persona cards from research inputs, marking unvalidated claims as proto-persona scaffolds.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product:generate-personaopusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produce one deliverable:
Produce one deliverable:
reports/01_ux/personas.md:
JOB- IDs) — When [situation], I want to [motivation], so I can [outcome],
covering functional / emotional / social dimensionsPER- IDs) — archetype, context & behaviors, JTBD, Pains, Gains, and a
verbatim quote (marked [proto] if unvalidated)Personas are anchored to jobs (which survive pivots), not to demographics. Unvalidated content is explicitly a proto-persona scaffold.
/product:generate-persona [--input=<file|dir>]... [--auto] [--lang=ja|en]
| Argument/Flag | Required | Description |
|---|---|---|
--input=<file|dir> | Recommended | Interview notes, surveys, analytics, support logs |
--auto | Optional | Skip elicitation; generate proto-personas from inputs only |
--lang | Optional | Override output language |
JOB- story.[proto]; emotional validity is weak until
research confirms it. Prefer research data wherever it exists.TBD in Open Questions.TBD/[proto]),
and a primary persona designated.| Input | Required/Recommended | Source | If missing/empty |
|---|---|---|---|
reports/00_core/vision-mission-value.md | Required | /product:define-vision | block with a message — personas need the target group |
research material (--input) | Recommended | User | proceed as proto-persona; mark [proto] |
work/context.md, work/traceability.json, --input.@rules/product/persona-jtbd.md.[proto]).JOB-/PER- nodes to work/traceability.json with Upstream
VIS- references.work/context.md; log TBD/[proto] items.reports/01_ux/personas.md, with JOB-/PER- ID tables (Upstream column) and the primary persona
flagged.
| Resource | Purpose |
|---|---|
@rules/product/persona-jtbd.md | JTBD job stories, persona cards, proto vs research-based |
| Skill | Relationship |
|---|---|
/product:define-vision | Upstream — provides the target group |
/product:map-journey | Downstream — maps the journey of each persona |
/product:define-features | Downstream — features serve JOB-/PER- |
/product:adapt-change | Re-runs this skill when the audience changes |
npx claudepluginhub wfukatsu/nexus-architect --plugin scalardbUse this skill when the user asks to "create user personas", "develop personas", "write a persona", "define our users", "user profile", "who is our user", "help me define the target user", "create a user archetype", or wants to build or update structured user persona definitions grounded in research or known user characteristics.
Generates structured personas and JTBD analysis with ODI job step tables, pain point mapping, and quantified success metrics. Use for Phase 1 user definition.
Generates behavioral user personas from product descriptions, user data, or research notes. Outputs 2-4 ranked personas with goals, pain points, behaviors, and product implications to personas-[product].md.