AGENT SKILL

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.

License 许可
Apache-2.0
最近更新
2026-11-14
Stars
★ 805
Forks
102

01 前言 Front Matter

name
foundation-persona
license
Apache-2.0
metadata
{ "author": "product-on-purpose", "updated": 1786838400000, "version": "2.6.1", "category": "research", "frameworks": [ "triple-diamond", "lean-startup", "design-thinking" ], "classification": "foundation" }
description
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.

02 资源文件 4

03 SKILL.md 正文

<!-- 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

  • product
  • marketing
  • buyer as input alias for marketing (output remains labeled 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

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:

  1. Resolve mode and intent Determine whether the request is product or marketing (buyer alias allowed). If mode is omitted, ask for mode selection. If execution must continue without reply, default to product and state that fallback explicitly.

  2. 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.

  3. Select exactly one template Use references/TEMPLATE.md and choose exactly one of:

    • Product Persona Template
    • Marketing Persona Template
  4. Generate a complete artifact Fill the selected template end-to-end:

    • header + one-sentence core-reality statement
    • metadata table
    • Persona Card
    • sections 1 through 11
    • Evidence & Confidence
  5. 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.
  6. Apply evidence and confidence policy

    • Use High|Medium|Low confidence with rationale.
    • Distinguish validated evidence from assumptions.
    • State open questions and governance follow-up.
  7. 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 (Product or Marketing) 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
  • [ ] buyer inputs are normalized to Marketing
  • [ ] Header, core-reality statement, metadata table, and Persona Card are present
  • [ ] All 1 through 11 sections 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, or Low with rationale
  • [ ] Validated, Assumed, Open questions, and Governance blocks are present
  • [ ] Template authoring notes (> guidance lines) are removed from the completed output

Examples

See references/EXAMPLE.md for a completed sample output.

04 同仓库更多 Skills

product-on-purpose
product-on-purpose/pm-skills

utility-update-pm-skills

Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-slideshow-creator

Generates professional presentations from a JSON deck specification using 18 slide types with dark/light variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-pm-workflow-orchestrator

Run an ordered sequence of pm-skills against one input, pausing for go/no-go and stopping on a failed or empty step. Accepts a saved prioritized action plan (Mode A) or an ad-hoc named chain (Mode B; the chain command routes here). Explicit invocation only; run --dry-run first while the native path is EXPERIMENTAL. To author a durable workflow instead, use utility-pm-workflow-builder.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-pm-workflow-builder

Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review. Runs overlap analysis against the existing workflows with a Why Gate, then helps select and sequence skills with authored handoffs. Use when creating a new multi-skill workflow or promoting a repeated ad-hoc chain into a durable one. To build a single skill instead, use utility-pm-skill-builder; to run a sequence without authoring anything, use the chain command or utility-pm-workflow-orchestrator.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-pm-skill-validate

Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.

★ 805
product-on-purpose
product-on-purpose/pm-skills

utility-pm-skill-iterate

Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.

★ 805