Pm-skills foundation-persona
Generates an evidence-calibrated product or marketing persona using the canonical v2.5 output contract. Use when shaping artifact perspective, stress-testing decisions, or framing product and GTM strategy.
git clone https://github.com/product-on-purpose/pm-skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/product-on-purpose/pm-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/foundation-persona" ~/.claude/skills/product-on-purpose-pm-skills-foundation-persona && rm -rf "$T"
skills/foundation-persona/SKILL.mdPersona Builder
This skill produces decision-usable personas from one canonical template pack.
Supported Modes
productmarketing
as input alias forbuyer
(output remains labeledmarketing
)Marketing
Generated
agent mode is out of scope for v2.5.0.
If the user asks for agent, ask them to choose product or marketing.
When to Use
- Before drafting PM or GTM artifacts that need a clear persona viewpoint
- When teams disagree on priorities and need behavior-grounded tradeoff framing
- When assumptions and confidence levels must be explicit for decision review
- When tailoring downstream work (PRD, stories, launch, messaging, enablement) to a specific user or buyer profile
Instructions
When asked to generate a persona, follow these steps:
-
Resolve mode and intent Determine whether the request is
orproduct
(marketing
alias allowed). If mode is omitted, ask for mode selection. If execution must continue without reply, default tobuyer
and state that fallback explicitly.product -
Collect context and evidence Use user-provided context first (goals, audience, domain, constraints, sources). If evidence is thin, continue generation but mark gaps and calibrate confidence.
-
Select exactly one template Use
and choose exactly one of:references/TEMPLATE.mdProduct Persona TemplateMarketing Persona Template
-
Generate a complete artifact Fill the selected template end-to-end:
- header + one-sentence core-reality statement
- metadata table
Persona Card- sections
through111 Evidence & Confidence
-
Enforce mode boundaries
- Product mode: focus on workflow behavior, decision patterns, friction, quality bar, and product tradeoffs.
- Marketing mode: focus on buying triggers, evaluation criteria, committee dynamics, objections, messaging, and GTM implications.
-
Apply evidence and confidence policy
- Use
confidence with rationale.High|Medium|Low - Distinguish validated evidence from assumptions.
- State open questions and governance follow-up.
- Use
-
Finalize for direct use Remove template guidance blockquotes (
notes) from the final output. Ensure narrative entries are concrete and decision-changing, not placeholder bullets.>
Output Contract (v2.5.0)
- Use one mode only (
orProduct
) per output.Marketing - Keep section numbering and headings from the selected template.
- Preserve the evidence table plus validated/assumed/open-questions/governance blocks.
Quality Checklist
Before finalizing, verify:
- Exactly one mode is used and clearly labeled
-
inputs are normalized tobuyerMarketing - Header, core-reality statement, metadata table, and
are presentPersona Card - All
through1
sections from the selected template are present and complete11 - Includes/not-valid boundaries are explicit in the metadata and narrative
- Evidence table is populated with concrete sources
- Confidence is
,High
, orMedium
with rationaleLow -
,Validated
,Assumed
, andOpen questions
blocks are presentGovernance - Template authoring notes (
guidance lines) are removed from the completed output>
Examples
See
references/EXAMPLE.md for a completed sample output.