
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.
- Installs
- 749
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/product-on-purpose/pm-skills --skill foundation-persona- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads foundation-persona automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Persona Builder
This skill produces decision-usable personas from one canonical template pack.
Supported Modes
productmarketingbuyeras input alias formarketing(output remains labeledMarketing)
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
When NOT to Use
- You need the job context rather than the person -> use
define-jtbd-canvas; the canvas captures what customers hire products to do, the persona captures who they are - You are mapping internal stakeholders, not customers -> use
discover-stakeholder-summary - You have raw interviews to synthesize first -> use
discover-interview-synthesis; a persona built on unsynthesized notes inherits their noise - No evidence exists at all and a real decision rides on the persona: gather research first; the skill labels assumptions honestly but cannot substitute for evidence
Instructions
When asked to generate a persona, follow these steps:
-
Resolve mode and intent Determine whether the request is
productormarketing(buyeralias allowed). If mode is omitted, ask for mode selection. If execution must continue without reply, default toproductand state that fallback explicitly. -
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
references/TEMPLATE.mdand choose exactly one of:Product 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
1through11 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
High|Medium|Lowconfidence with rationale. - 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 (
ProductorMarketing) per output. - 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
-
buyerinputs are normalized toMarketing - Header, core-reality statement, metadata table, and
Persona Cardare present - All
1through11sections from the selected template are present and complete - Includes/not-valid boundaries are explicit in the metadata and narrative
- Evidence table is populated with concrete sources
- Confidence is
High,Medium, orLowwith rationale -
Validated,Assumed,Open questions, andGovernanceblocks are present - Template authoring notes (
>guidance lines) are removed from the completed output
Examples
See references/EXAMPLE.md for a completed sample output.
FAQ
What does the foundation-persona skill do?
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.
How do I install foundation-persona?
Run npx skills add https://github.com/product-on-purpose/pm-skills --skill foundation-persona in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/foundation-persona/ (personal) or .claude/skills/foundation-persona/ (project).
Which AI agents can use foundation-persona?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is foundation-persona safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains foundation-persona?
It is published by product-on-purpose in product-on-purpose/pm-skills. It has 749 recorded installs.
More from product-on-purpose/pm-skills
deliver-acceptance-criteria
product-on-purpose/pm-skills
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.
deliver-prd
product-on-purpose/pm-skills
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
deliver-user-stories
product-on-purpose/pm-skills
Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.
deliver-edge-cases
product-on-purpose/pm-skills
Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary and limit scenarios to test. Distinct from deliver-acceptance-criteria, which writes story-level Given/When/Then checks; this skill produces the whole-feature edge-case catalog.
discover-competitive-analysis
product-on-purpose/pm-skills
Creates a structured competitive analysis comparing features, pricing, and positioning across 3-5 direct and indirect competitors, with a 2x2 map and actionable strategic recommendations. Use before entering a market, planning differentiation, or after losing deals. For market size rather than competitor positioning, use discover-market-sizing instead.
define-problem-statement
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work