foundation-persona
Skill777 starsChanged 10 months agoApache-2.0View on GitHub
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.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- define-hypothesisSkill
- define-jtbd-canvasSkill
- define-opportunity-treeSkill
- define-prioritization-frameworkSkill
- define-problem-statementSkill
- deliver-acceptance-criteriaSkill
- deliver-edge-casesSkill
- deliver-launch-checklistSkill
- deliver-prdSkill
- deliver-release-notesSkill
- deliver-user-storiesSkill
- develop-adrSkill
- develop-design-rationaleSkill
- develop-solution-briefSkill
- develop-spike-summarySkill
- discover-competitive-analysisSkill
- discover-interview-synthesisSkill
- discover-journey-mapSkill
- discover-market-sizingSkill
- discover-stakeholder-summarySkill
- foundation-build-risk-reviewSkill
- foundation-lean-canvasSkill
- foundation-meeting-agendaSkill
- foundation-meeting-briefSkill
- foundation-meeting-recapSkill
- foundation-meeting-synthesizeSkill
- foundation-okr-writerSkill
- foundation-prioritized-action-planSkill
- foundation-stakeholder-briefingsSkill
- foundation-stakeholder-updateSkill
- iterate-lessons-logSkill
- iterate-pivot-decisionSkill
- iterate-refinement-notesSkill
- iterate-retrospectiveSkill
- measure-dashboard-requirementsSkill
- measure-experiment-designSkill
- measure-experiment-resultsSkill
- measure-instrumentation-specSkill
- measure-okr-graderSkill
- measure-survey-analysisSkill
- tool-design-sprint-briefSkill
- tool-design-sprint-decide-and-storyboardSkill
- tool-design-sprint-map-and-targetSkill
- tool-design-sprint-prototype-planSkill
- tool-design-sprint-readinessSkill
- tool-design-sprint-sketchSkill
- tool-design-sprint-test-and-scoreSkill
- tool-foundation-sprint-approach-optionsSkill
- tool-foundation-sprint-basicsSkill
- tool-foundation-sprint-briefSkill
- tool-foundation-sprint-differentiationSkill
- tool-foundation-sprint-founding-hypothesisSkill
- tool-foundation-sprint-magic-lensesSkill
- tool-foundation-sprint-readinessSkill
- tool-note-and-voteSkill
- utility-mermaid-diagramsSkill
- utility-pm-changelog-curatorSkill
- utility-pm-criticSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 10 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
If the user asks for agent, ask them to choose product or marketing.
- Distinctive: line 29
Before drafting PM or GTM artifacts that need a clear persona viewpoint
- Distinctive: line 30
When teams disagree on priorities and need behavior-grounded tradeoff framing
- Distinctive: line 31
When assumptions and confidence levels must be explicit for decision review
- Distinctive: line 32
When tailoring downstream work (PRD, stories, launch, messaging, enablement) to a specific user or buyer profile
- Distinctive: line 39
No evidence exists at all and a real decision rides on the persona: gather research first.
- Distinctive: line 43
When asked to generate a persona, follow these steps:
- Very specific: line 47
If mode is omitted, ask for mode selection.
- Very specific: line 48
If execution must continue without reply, default to product and state that fallback explicitly.
- Distinctive: line 51
Use user-provided context first (goals, audience, domain, constraints, sources).
- Distinctive: line 52
If evidence is thin, continue generation but mark gaps and calibrate confidence.
- Very specific: line 55
Use references/TEMPLATE.md and choose exactly one of:
- Very specific: line 72
Use High|Medium|Low confidence with rationale.
- Very specific: line 77
Remove template guidance blockquotes (> notes) from the final output.
- Distinctive: line 78
Ensure narrative entries are concrete and decision-changing, not placeholder bullets.
- Very specific: line 82
Use one mode only (Product or Marketing) per output.
- Distinctive: line 83
Keep section numbering and headings from the selected template.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

