pm-persona-codifier

Codify raw customer research into source-attributed persona documents with a fixed 9-section template.

Updated May 3, 2026
One-click install
npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill pm-persona-codifier-spikelab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-persona-codifier
Source: https://github.com/spikelab/multiplai-cc-mktplace/tree/main/plugins/multiplai-pm/skills/pm-persona-codifier
Command: npx skills add https://github.com/spikelab/multiplai-cc-mktplace --skill pm-persona-codifier-spikelab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Product teams accumulate interview transcripts, JTBD notes, and archetype hypotheses but lack canonical persona documents that downstream PRDs, strategy memos, and roadmaps can reference consistently. This Skill turns scattered source material into structured, quote-anchored persona files without fabricating detail. ## Core Features & Use Cases - Signal clustering: Groups source material into up to 5 personas along five axes (job clusters, decision role, context of use, definition of success, anxieties), with merge/pushback logic. - 9-section canonical template: Emits one persona file per archetype covering snapshot, jobs, stated vs. actual wants, decision process, attributed quotes, product implications, anti-persona, and open questions. - Cross-checks and INDEX: Runs overlap, contradiction, completeness, and anti-persona checks, then writes an INDEX.md flagging tensions and under-evidenced personas. - Use Case: After running JTBD synthesis on customer interviews, ask the Skill to codify the job clusters into buyer and user personas with quote-level attribution, producing files your strategy memo can reference by ID. ## Quick Start Codify the interview transcripts in my research folder into persona documents using the JTBD synthesis output as input.

Frequently Asked Questions about pm-persona-codifier

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

FAQPage Schema
How do I turn customer interview transcripts into persona documents?

Provide the transcripts as the source argument and the Skill clusters signals into personas, fills a 9-section template per persona, and anchors every claim to source line numbers. Output is one Markdown file per persona plus an INDEX with cross-persona tensions.

Should I do JTBD synthesis before creating personas?

Yes, jobs come first. Personas built on JTBD job clusters are more durable because they bundle jobs with decision context and emotional posture. The Skill works without JTBD output but flags the personas as shakier in Open Questions.

How many personas should a product team define?

The Skill caps output at 5 personas and pushes back on more. Beyond 5, personas usually represent under-clustering and dilute the team's shared mental model of the customer.

What happens when there is not enough interview evidence for a persona?

The Skill flags under-evidenced personas rather than fabricating detail. A persona with fewer than 3 attributed quotes is marked as a hypothesis in Open Questions and the INDEX confidence notes.

Can buyer and user personas be merged in B2B products?

No. When buyers and users are different people, the Skill keeps them as separate personas because their definitions of success and decision processes differ fundamentally.