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.
What this skill does
<!-- 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 ## 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.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.