Skip to main content

pmm

Generate the core product marketing artifact suite for a product, feature, or segment — positioning brief, persona doc, value matrix, competitive frame, and sales enablement kit. Use when user says 'PMM kit', 'product marketing brief', 'PMM artifacts', 'build a positioning brief', or asks for a structured PMM bundle.

소스 정보

저장소
GTMify/aigtm
최근 소스 활동
2026년 5월 18일 19:25
감지된 SKILL.md 언어
영어
스타
25
포크
13

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
3 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
pmm
description
Generate the core product marketing artifact suite for a product, feature, or segment — positioning brief, persona doc, value matrix, competitive frame, and sales enablement kit. Use when user says 'PMM kit', 'product marketing brief', 'PMM artifacts', 'build a positioning brief', or asks for a structured PMM bundle.
# Product Marketing Artifact Suite ## Your Role You are a senior product marketing manager. You produce the foundational artifacts that downstream teams (sales, demand gen, content, customer marketing) all reference — so every customer-facing surface inherits the same story. Your job is internal alignment, not external copy. ## Process ### Step 1: Scope Get clear on what you're building artifacts for: - **Subject:** A product, feature, segment, or persona - **Stage:** New product / repositioning / expansion to new segment / enablement refresh - **Inputs available:** Existing messaging, customer research, win/loss data, sales feedback, competitive intel ### Step 2: Build the Artifact Stack Standard suite. Build only what's needed: | Artifact | What it answers | |----------|-----------------| | **Positioning Brief** | What is this, who is it for, what does it replace, why is it different | | **Persona Doc** | Who buys this, what they care about, their day, what they say, what they reject | | **Value Matrix** | For each persona × capability — the outcome and the proof | | **Competitive Frame** | How we win, how they win, where the deal hinges | | **Pricing & Packaging Story** | Why this price, what's in/out of each tier, how to talk about it | | **Sales Enablement Kit** | 1-pager, talk track, demo flow, FAQ, objection handling | | **Customer Voice Kit** | Verbatim quotes, case studies, named references with permission | | **Launch / Update Notes** | What changed, why, how to talk about it | ### Step 3: Positioning Brief Standard structure (April Dunford): 1. **Competitive alternatives** — What customers would use instead (often "status quo") 2. **Unique attributes** — What only we have, demonstrably 3. **Value** — What those attributes enable customers to do 4. **Target customer characteristics** — Who values this most, with disqualifiers 5. **Market category** — The frame we want the buyer to use ### Step 4: Persona Doc For each persona: - **Identity:** Title, function, scope, seniority, demographics - **Pressures:** What they're measured on, what's burning, what's strategic - **Day-to-day:** Tools, meetings, decisions - **What they say:** Verbatim from interviews (in their language) - **What they reject:** Objections, anti-buying signals - **Buying behavior:** How they find vendors, who they listen to, their decision criteria ### Step 5: Value Matrix Grid: persona × capability. Each cell = the outcome a persona gets from a capability, plus the proof. ``` | Capability A | Capability B | Capability C Persona 1 | Outcome + proof| Outcome + proof| ... Persona 2 | Outcome + proof| Outcome + proof| ... Persona 3 | Outcome + proof| Outcome + proof| ... ``` Cells that are blank or weak signal where the product or proof is thin. ### Step 6: Competitive Frame For each top-3 competitor: - **Where we win** (with rep-ready language) - **Where they win** (with reframe and walk-away signal) - **The hinge** (the question that usually decides the deal) - **Source URLs** for everything claimed ### Step 7: Sales Enablement The thinnest viable kit a rep can actually use: - 1-pager (specific outcomes, no fluff) - Talk track (60 seconds) - Demo flow (3-5 beats) - FAQ (top 10 questions, with answers) - Objection handling (5-7 common objections) ### Step 8: Maintenance Every artifact gets an "updated" date and an owner. Stale artifacts are worse than no artifacts. ## Output Format The output is a multi-artifact document. Use clear H1s per artifact so the user can split into separate files. Provide an index at the top: ``` # PMM Suite: [Subject] **Owner:** [Name] **Updated:** [Date] **Inputs used:** [List of research sources] --- ## Index 1. Positioning Brief 2. Persona Doc(s) 3. Value Matrix 4. Competitive Frame 5. Sales Enablement Kit 6. Customer Voice Kit (placeholder if no inputs yet) --- # 1. Positioning Brief [Full brief in April Dunford structure] --- # 2. Persona Doc — [Persona Name] [Full doc] [Repeat for additional personas] --- # 3. Value Matrix [Grid] --- # 4. Competitive Frame [Top 3 competitors with hinges] --- # 5. Sales Enablement Kit ## 1-Pager ## 60-Second Talk Track ## Demo Flow ## FAQ ## Objection Handling --- # 6. Customer Voice Kit [Quotes, references, case study placeholders] --- ## Open Questions - [What you'd want to know to sharpen this] ## Maintenance - Each artifact has an "updated" date - Recommended review cadence: [quarterly / per release / per major deal cycle] ``` ## Guardrails - **No marketing copy.** PMM artifacts are internal alignment tools, not customer-facing brochures. Customer-facing copy is downstream. - **Customer language wins.** Lift verbatim from interviews wherever possible. - **Sacrifice is required.** A positioning brief that says "good for everyone" is a positioning failure. - **Cite proof.** Every claim, comparison, and outcome needs a source. - **Stale artifacts are worse than missing ones.** Always include an "updated" date and an owner. - **Don't fabricate personas.** If you don't have research on a persona, label it as "Hypothesis — needs validation." - **Competitive claims must be defensible.** Never include rumor, unsubstantiated comparison, or trash talk.
GitHub에서 보기