v1.0

pm-toolkit/.claude-plugin/plugin.json

@@ -0,0 +1,20 @@
+{
+  "name": "pm-toolkit",
+  "version": "1.0.0",
+  "description": "PM utility skills: resume review, NDA drafting, privacy policy generation, and grammar/flow checking. Essential tools for product managers beyond core product work.",
+  "author": {
+    "name": "Paweł Huryn",
+    "email": "pawel@productcompass.pm",
+    "url": "https://www.productcompass.pm"
+  },
+  "keywords": [
+    "product-management",
+    "resume",
+    "legal",
+    "nda",
+    "privacy-policy",
+    "copywriting"
+  ],
+  "homepage": "https://www.productcompass.pm",
+  "license": "MIT"
+}

pm-toolkit/README.md

@@ -0,0 +1,43 @@
+# pm-toolkit
+
+PM utility skills: resume review, NDA drafting, privacy policy generation, and grammar/flow checking. Essential tools for product managers beyond core product work.
+
+## Overview
+
+This plugin provides 5 skills and 5 commands for product managers.
+
+## Skills
+
+- **adjust-resume** — Tailor a PM resume to a specific job description.
+- **draft-nda** — Draft a detailed Non-Disclosure Agreement between two parties.
+- **grammar-check** — Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text.
+- **privacy-policy** — Draft a detailed privacy policy for a product covering data types, jurisdiction, compliance considerations, and claus...
+- **review-resume** — Comprehensive PM resume review against 10 best practices including XYZ+S formula, keyword optimization, and structure.
+
+## Commands
+
+- `/pm-toolkit:draft-nda` — Draft a Non-Disclosure Agreement between two parties with jurisdiction-appropriate clauses
+- `/pm-toolkit:privacy-policy` — Draft a privacy policy covering data collection, usage, storage, and compliance requirements
+- `/pm-toolkit:proofread` — Check grammar, logic, and flow in any text — targeted fixes without rewriting
+- `/pm-toolkit:review-resume` — Comprehensive PM resume review against 10 best practices — structure, impact metrics, keywords, and actionable feedback
+- `/pm-toolkit:tailor-resume` — Tailor a PM resume to a specific job description — keyword alignment, experience reframing, and strategic optimization
+
+## Installation
+
+```bash
+/install pm-toolkit
+```
+
+Or use directly:
+
+```bash
+cc --plugin-dir /path/to/pm-toolkit
+```
+
+## Author
+
+Paweł Huryn — [The Product Compass Newsletter](https://www.productcompass.pm)
+
+## License
+
+MIT

pm-toolkit/commands/draft-nda.md

@@ -0,0 +1,66 @@
+---
+description: Draft a Non-Disclosure Agreement between two parties with jurisdiction-appropriate clauses
+argument-hint: "<parties and context>"
+---
+
+# /draft-nda -- NDA Drafting
+
+Draft a professional Non-Disclosure Agreement customized to your situation. Covers information types, jurisdiction, term, and clearly marks clauses that need legal review.
+
+## Invocation
+
+```
+/draft-nda Mutual NDA between our startup and a potential enterprise customer
+/draft-nda One-way NDA for a freelance contractor accessing our codebase
+```
+
+## Workflow
+
+### Step 1: Gather Context
+
+Ask:
+- Who are the parties? (company names and roles)
+- Mutual or one-way NDA?
+- What information is being protected? (trade secrets, code, business data, customer data)
+- Jurisdiction? (state/country for governing law)
+- Duration? (how long should confidentiality last)
+- Any specific concerns? (non-compete, non-solicit, IP ownership)
+
+### Step 2: Draft the NDA
+
+Apply the **draft-nda** skill:
+
+Generate a complete NDA covering:
+- Parties and recitals
+- Definition of confidential information (with specific examples)
+- Obligations of the receiving party
+- Exclusions (public knowledge, independent development, etc.)
+- Term and survival
+- Return/destruction of materials
+- Remedies
+- Governing law and jurisdiction
+- Standard boilerplate (severability, entire agreement, amendments)
+
+### Step 3: Deliver
+
+```
+## Non-Disclosure Agreement
+
+[Full NDA text with marked sections]
+
+### Clauses Requiring Legal Review
+| Clause | Why It Needs Review | Consideration |
+|--------|-------------------|--------------|
+
+### Plain-Language Summary
+[What this NDA means in simple terms for non-lawyers]
+```
+
+Save as markdown. Offer to export as DOCX for signing.
+
+## Notes
+
+- This is a starting point — always recommend review by qualified legal counsel
+- Mark any clause that involves significant legal risk with a ⚠️ flag
+- Include plain-language annotations so non-lawyers understand what they're agreeing to
+- Mutual NDAs are generally preferred — they're fairer and faster to negotiate

pm-toolkit/commands/privacy-policy.md

@@ -0,0 +1,76 @@
+---
+description: Draft a privacy policy covering data collection, usage, storage, and compliance requirements
+argument-hint: "<product and data handling context>"
+---
+
+# /privacy-policy -- Privacy Policy Generator
+
+Draft a comprehensive privacy policy for your product. Covers data types, jurisdiction, compliance (GDPR, CCPA), and marks clauses needing legal review.
+
+## Invocation
+
+```
+/privacy-policy SaaS analytics tool that collects user behavior data — serving US and EU customers
+/privacy-policy Mobile app with location data and third-party integrations
+```
+
+## Workflow
+
+### Step 1: Gather Context
+
+Ask:
+- What product or service?
+- What data is collected? (personal info, usage data, cookies, location, payment)
+- Where are your users? (determines applicable regulations: GDPR, CCPA, etc.)
+- Any third-party data sharing? (analytics, advertising, integrations)
+- Data storage: where and how long?
+- Age restrictions? (COPPA considerations)
+
+### Step 2: Draft the Policy
+
+Apply the **privacy-policy** skill:
+
+Generate sections covering:
+- What data is collected and how
+- How data is used (purposes)
+- Legal basis for processing (GDPR)
+- Data sharing and third parties
+- Data retention and deletion
+- User rights (access, deletion, portability, opt-out)
+- Cookie policy
+- Security measures
+- Children's privacy (if applicable)
+- International transfers
+- Contact information
+- Policy update process
+
+### Step 3: Deliver
+
+```
+## Privacy Policy: [Product]
+
+[Full policy text]
+
+### Compliance Checklist
+| Regulation | Status | Notes |
+|-----------|--------|-------|
+
+### Clauses Requiring Legal Review
+| Clause | Why | Priority |
+|--------|-----|----------|
+
+### Implementation Checklist
+- [ ] Cookie consent banner
+- [ ] Data subject request process
+- [ ] Data processing records
+- [ ] DPA with processors
+```
+
+Save as markdown. Offer DOCX export.
+
+## Notes
+
+- This is a template — legal counsel should review before publishing
+- GDPR and CCPA have specific requirements that can't be approximated — flag where expert review is essential
+- Privacy policies should be in plain language, not legalese
+- Update the policy when data practices change, not just annually

pm-toolkit/commands/proofread.md

@@ -0,0 +1,67 @@
+---
+description: Check grammar, logic, and flow in any text — targeted fixes without rewriting
+argument-hint: "<text to check>"
+---
+
+# /proofread -- Grammar & Flow Check
+
+Identify grammar, logical, and flow errors in text. Provides specific, targeted fixes without rewriting the entire document.
+
+## Invocation
+
+```
+/proofread [paste text]
+/proofread [upload a document]
+```
+
+## Workflow
+
+### Step 1: Accept Text
+
+Accept text in any form: pasted, uploaded document (DOCX, PDF, markdown), or email draft.
+
+### Step 2: Analyze
+
+Apply the **grammar-check** skill:
+
+Scan for three categories of issues:
+
+**Grammar**: Spelling, punctuation, subject-verb agreement, tense consistency, article usage
+**Logic**: Contradictions, unsupported claims, circular reasoning, unclear references
+**Flow**: Awkward transitions, sentence rhythm, paragraph structure, redundancy, readability
+
+### Step 3: Report Issues
+
+```
+## Proofread Report
+
+**Text length**: [word count]
+**Issues found**: [count by category]
+
+### Issues
+
+#### 1. [Category: Grammar/Logic/Flow]
+- **Location**: "[quoted text with issue]"
+- **Issue**: [what's wrong]
+- **Fix**: "[corrected text]"
+
+[Repeat for each issue]
+
+### Summary
+- Grammar: [X] issues
+- Logic: [X] issues
+- Flow: [X] issues
+- Overall quality: [assessment]
+```
+
+### Step 4: Offer
+
+- "Want me to **apply all fixes** and return the cleaned text?"
+- "Should I **focus on a specific section** in more detail?"
+
+## Notes
+
+- Fix suggestions should be minimal — change only what's needed, preserve the author's voice
+- For non-native English speakers, be especially clear about *why* a change is suggested
+- Don't over-correct style preferences — there's a difference between wrong and different
+- For professional documents, also check for tone consistency and audience appropriateness

pm-toolkit/commands/review-resume.md

@@ -0,0 +1,88 @@
+---
+description: Comprehensive PM resume review against 10 best practices — structure, impact metrics, keywords, and actionable feedback
+argument-hint: "<resume as text or file>"
+---
+
+# /review-resume -- PM Resume Review
+
+Get a thorough resume review against product management best practices. Evaluates structure, impact metrics, keyword optimization, and provides specific improvement suggestions with examples.
+
+## Invocation
+
+```
+/review-resume [paste resume text]
+/review-resume [upload resume PDF or DOCX]
+```
+
+## Workflow
+
+### Step 1: Accept the Resume
+
+Accept as pasted text, uploaded PDF, or DOCX file. Parse the full content.
+
+### Step 2: Evaluate Against 10 Best Practices
+
+Apply the **review-resume** skill:
+
+1. **Impact Metrics**: Are accomplishments quantified? (revenue, users, conversion rates)
+2. **XYZ+S Formula**: "Accomplished [X] as measured by [Y], by doing [Z] using [S skill/tool]"
+3. **PM-Specific Language**: Uses product terminology (shipped, led discovery, defined strategy)
+4. **Structure & Readability**: Clear sections, consistent formatting, scannable
+5. **Keyword Optimization**: Matches common PM job description keywords
+6. **Story Arc**: Shows career progression and increasing scope
+7. **Brevity**: One page (junior), two pages max (senior). No fluff.
+8. **Relevance**: Experience tailored to PM roles, not generic
+9. **Technical Credibility**: Demonstrates working with engineering, data, design
+10. **Leadership Signals**: Cross-functional influence, stakeholder management, mentoring
+
+### Step 3: Generate Review
+
+```
+## Resume Review
+
+**Overall Score**: [X/10]
+**Strongest area**: [which best practice]
+**Biggest opportunity**: [which best practice]
+
+### Scorecard
+| # | Best Practice | Score | Assessment |
+|---|-------------|-------|-----------|
+| 1 | Impact Metrics | [/10] | [brief assessment] |
+| 2 | XYZ+S Formula | [/10] | [brief assessment] |
+| ... | ... | ... | ... |
+
+### Top 3 Improvements
+
+**1. [Most impactful change]**
+- Current: "[exact text from resume]"
+- Suggested: "[improved version]"
+- Why: [reasoning]
+
+**2. [Second improvement]**
+[same format]
+
+**3. [Third improvement]**
+[same format]
+
+### Section-by-Section Feedback
+[Specific notes for each resume section: summary, experience, education, skills]
+
+### Missing Elements
+[What's absent that should be present for a PM resume]
+
+### Keywords to Add
+[PM-relevant keywords missing from the resume that appear in typical job descriptions]
+```
+
+### Step 4: Offer Next Steps
+
+- "Want me to **tailor this resume** to a specific job description?"
+- "Should I **rewrite specific bullet points** using the XYZ+S formula?"
+- "Want me to **generate a cover letter** based on this resume?"
+
+## Notes
+
+- Be specific and constructive — "add metrics" is unhelpful, "change 'improved onboarding' to 'reduced onboarding drop-off by 23% (450 → 347 users/month)'" is actionable
+- PM resumes should emphasize outcomes over outputs, influence over authority
+- ATS (Applicant Tracking System) optimization matters — mention relevant keywords naturally
+- Different PM levels have different expectations: APM = potential, Senior PM = impact, Director+ = scale

pm-toolkit/commands/tailor-resume.md

@@ -0,0 +1,81 @@
+---
+description: Tailor a PM resume to a specific job description — keyword alignment, experience reframing, and strategic optimization
+argument-hint: "<resume> + <job description>"
+---
+
+# /tailor-resume -- Resume-to-JD Optimization
+
+Take your resume and a target job description, then strategically align your experience to maximize interview chances. Keyword optimization, bullet point rewriting, and gap analysis.
+
+## Invocation
+
+```
+/tailor-resume [upload resume] Here's the JD: [paste job description]
+/tailor-resume [upload both resume and JD as files]
+```
+
+## Workflow
+
+### Step 1: Accept Both Documents
+
+Need two inputs:
+- The resume (text, PDF, or DOCX)
+- The target job description (text, URL, or file)
+
+If only one is provided, ask for the other.
+
+### Step 2: Analyze the Job Description
+
+Extract:
+- Required qualifications and skills
+- Preferred qualifications
+- Key responsibilities
+- Industry and domain signals
+- Seniority level indicators
+- Cultural and team signals
+
+### Step 3: Tailor the Resume
+
+Apply the **review-resume** skill:
+
+- **Keyword alignment**: Map JD keywords to resume content, add missing keywords naturally
+- **Bullet point rewriting**: Reframe experience to emphasize JD-relevant accomplishments using XYZ+S formula
+- **Section reordering**: Prioritize the most relevant experience
+- **Summary/objective**: Rewrite to directly address the role
+- **Skills section**: Align with JD requirements
+
+### Step 4: Generate Tailored Resume + Analysis
+
+```
+## Resume Tailoring: [Job Title] at [Company]
+
+### Alignment Score: [X/10]
+
+### Keyword Gap Analysis
+| JD Keyword | In Resume? | Recommendation |
+|-----------|-----------|---------------|
+
+### Changes Made
+1. **[Section]**: [what changed and why]
+2. ...
+
+### Tailored Resume
+[Full rewritten resume text]
+
+### Gap Analysis
+**Strong matches**: [where your experience directly aligns]
+**Reframed matches**: [where experience was repositioned to fit]
+**Gaps**: [JD requirements you don't clearly address — with suggestions]
+
+### Cover Letter Talking Points
+[3-4 points to emphasize in a cover letter that bridge remaining gaps]
+```
+
+Save tailored resume as markdown.
+
+## Notes
+
+- Never fabricate experience — reframe truthfully, don't invent
+- The summary/objective is the highest-ROI section to customize per application
+- Match the JD's language exactly where possible (if they say "cross-functional," use "cross-functional")
+- For senior roles, emphasize scale and strategic impact; for IC roles, emphasize hands-on execution

pm-toolkit/skills/draft-nda/SKILL.md

@@ -0,0 +1,160 @@
+---
+name: draft-nda
+description: "Draft a detailed Non-Disclosure Agreement between two parties. Covers information types, jurisdiction, and highlights clauses needing legal review. Triggers: NDA, non-disclosure agreement, confidentiality agreement."
+---
+# NDA (Non-Disclosure Agreement) Drafting
+
+You are an experienced legal document specialist with expertise in confidentiality agreements. Your role is to help draft detailed, clear, and professional Non-Disclosure Agreements between parties.
+
+## Purpose
+Draft a comprehensive Non-Disclosure Agreement (NDA) between two parties. The NDA covers information types, jurisdiction, and clearly marks clauses that require legal review. Provide plain-language explanations to make the document accessible.
+
+## Important Disclaimer
+**This is for informational purposes only and does not constitute legal advice. Always have a licensed attorney review the final document before execution. NDAs are legally binding contracts; professional legal review is essential.**
+
+## Input Arguments
+- `$COMPANY_ONE_NAME`: Name of the first party/company
+- `$COMPANY_ONE_ADDRESS`: Address of the first party/company
+- `$COMPANY_ONE_REPS`: Names and titles of representatives (e.g., "John Smith, CEO; Jane Doe, General Counsel")
+- `$COMPANY_TWO_NAME`: Name of the second party/company
+- `$COMPANY_TWO_ADDRESS`: Address of the second party/company
+- `$COMPANY_TWO_REPS`: Names and titles of representatives
+- `$INFORMATION_TYPES`: Types of information to be shared (e.g., "business plans, customer lists, technical specifications, pricing data, source code")
+- `$JURISDICTION`: Governing jurisdiction (e.g., "State of California, United States" or "England and Wales")
+
+## Process
+
+### Step 1: Clarify Requirements
+Before drafting, note down:
+- Are both parties companies or is one an individual?
+- What specific types of information will be shared?
+- Is this one-way (only one party shares) or mutual (both parties share)?
+- What is the geographic jurisdiction?
+- What is the intended duration of the NDA?
+
+### Step 2: Structure the NDA
+Organize the NDA in standard sections:
+
+1. **Preamble** (Parties, definitions, effective date)
+2. **Definitions** (What is "Confidential Information"?)
+3. **Obligation to Maintain Confidentiality** (Core obligation)
+4. **Permitted Disclosures** (Exceptions to confidentiality)
+5. **Term and Duration** (How long does the NDA last?)
+6. **Return or Destruction of Information** (What happens after?)
+7. **Remedies** (Consequences for breach)
+8. **General Provisions** (Governing law, jurisdiction, severability)
+
+### Step 3: Use Plain Language
+Write each section in clear, accessible language. Avoid legal jargon where possible. Define terms the first time they're used.
+
+### Step 4: Highlight Clauses Needing Legal Review
+Mark sections with [⚠️ LEGAL REVIEW REQUIRED] where customization or specific legal expertise is needed. Include explanations of what should be reviewed.
+
+### Step 5: Provide Context
+Include brief notes explaining:
+- Why each section is important
+- What decisions need to be made by the parties
+- Common pitfalls or considerations
+
+## NDA Template Structure
+
+Present the draft NDA in this order:
+
+**[COVER NOTE]**
+A brief note explaining the NDA's purpose, the parties involved, and key provisions.
+
+**[FULL NDA DOCUMENT]**
+The complete agreement ready for customization.
+
+**[NOTES ON KEY CLAUSES]**
+Explanations of important sections and what may need legal customization.
+
+---
+
+## Key Sections to Include
+
+### Preamble
+- Introduce both parties clearly with full legal names and addresses
+- State the purpose: exploring a potential business relationship, partnership, merger, etc.
+- Define the "Effective Date"
+
+### Definitions
+- **Confidential Information**: Specify what is considered confidential (business plans, financial data, technical specs, customer lists, etc.). Include scope.
+- **Excluded Information**: Clarify what is NOT confidential (publicly available information, information independently developed, information received from third parties without confidentiality obligations)
+
+### Obligations
+- Describe the receiving party's duty to keep information confidential
+- Specify approved uses of the information
+- Outline permitted disclosures (to employees, advisors, on a need-to-know basis)
+- [⚠️ LEGAL REVIEW REQUIRED] Standard of care (e.g., "same care as own confidential information, but no less than reasonable care")
+
+### Permitted Disclosures
+- Specify who can be told (employees, advisors, consultants on a need-to-know basis)
+- Include a requirement that recipients also agree to confidentiality
+- Add exception for legally required disclosures (with notice requirement, if possible)
+
+### Term and Duration
+- Define the period during which information is being shared
+- Define how long confidentiality obligations survive after the relationship ends
+- [⚠️ LEGAL REVIEW REQUIRED] Consider different durations for different information types (trade secrets may require longer protection)
+
+### Return or Destruction
+- Specify that the receiving party must return or securely destroy confidential information upon request or upon termination
+- Option to certify in writing that destruction is complete
+- Consider: does the receiving party keep one copy for legal compliance?
+
+### Remedies
+- [⚠️ LEGAL REVIEW REQUIRED] State that breach may cause irreparable harm and that injunctive relief is available
+- Clarify that remedies are in addition to other legal remedies available
+
+### General Provisions
+- **Governing Law and Jurisdiction**: Specify which state or country's laws govern (e.g., California or England)
+- [⚠️ LEGAL REVIEW REQUIRED] Dispute resolution process (litigation, arbitration, mediation)
+- **Severability**: If one provision is invalid, others remain in force
+- **Entire Agreement**: This NDA supersedes prior discussions
+- **Amendments**: Specify that NDA can only be modified in writing, signed by both parties
+- **Counterparts**: Parties can sign separate copies
+
+---
+
+## Content Guidelines
+
+- **Plain Language**: Write for a primary-school-educated reader. Avoid Latin phrases, unnecessary legal terms.
+- **Clarity over Precision**: Choose clear language first. Legal precision can be refined by attorneys.
+- **Examples**: Where helpful, include examples of what is/isn't confidential information.
+- **Specific Information Types**: Use the $INFORMATION_TYPES provided to make the agreement specific, not generic.
+- **Mutual or One-Way**: If $INFORMATION_TYPES suggests only one party is sharing, note this as a one-way NDA. If both, use mutual language.
+
+---
+
+## Output Format
+
+Present the NDA in three parts:
+
+### Part 1: Summary
+Bullet-point overview of:
+- Parties involved
+- Information types covered
+- Key duration and terms
+- Jurisdiction
+
+### Part 2: Full NDA Document
+A complete, ready-to-customize NDA document.
+
+### Part 3: Customization Notes
+Guidance on:
+- Sections marked for legal review
+- Decisions parties need to make
+- Common modifications based on situation
+- Next steps (legal review, signing process)
+
+---
+
+## Important Reminders
+
+- This is a starting point, not final legal advice
+- Jurisdictions vary widely; have a lawyer in the relevant jurisdiction review
+- Some industries (tech, pharma, finance) have specific NDA conventions
+- Consider mutual vs. one-way requirements
+- Think about duration: How long should the information be protected?
+- Always have an attorney review before any party signs

pm-toolkit/skills/grammar-check/SKILL.md

@@ -0,0 +1,209 @@
+---
+name: grammar-check
+description: "Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content or checking writing quality. Triggers: grammar check, proofread, check my writing, fix grammar."
+---
+# Grammar and Flow Checking
+
+You are an expert copyeditor and writing specialist. Your role is to identify grammar, logical, and flow errors in text, then provide clear, actionable fix suggestions without rewriting the entire document.
+
+## Purpose
+Analyze text for grammar, logical, and flow errors. Provide specific, focused suggestions on how to fix each issue. Focus on clarity, correctness, and readability.
+
+## Input Arguments
+- `$OBJECTIVE`: What is the intended purpose or goal of the text? (e.g., "persuade investors to fund our Series A," "explain product features to new users," "communicate company values to employees")
+- `$TEXT`: The text to review
+
+## Process
+
+### Step 1: Understand Context
+- Note the objective: Is this marketing copy, technical documentation, a presentation, an email, social media content?
+- Identify the target audience: Experts, general public, stakeholders, customers?
+- Consider tone: Formal, casual, authoritative, friendly?
+
+### Step 2: Scan for Errors
+Read through the text once, identifying:
+- **Grammar errors**: Spelling, punctuation, subject-verb agreement, tense consistency, modifier placement
+- **Logical errors**: Contradictions, unsupported claims, unclear cause-and-effect, incomplete thoughts
+- **Flow errors**: Choppy transitions, unclear organization, redundancy, passive voice overuse, vague pronouns, awkward phrasing
+
+### Step 3: Categorize Errors
+Organize findings by type:
+1. Grammar (spelling, punctuation, syntax)
+2. Logic (clarity, coherence, reasoning)
+3. Flow (transitions, sentence structure, readability, tone consistency)
+
+### Step 4: Create Fix Suggestions
+For each error, provide:
+- **Location**: Where in the text (e.g., "Paragraph 3, sentence 2")
+- **Error identified**: What's wrong
+- **Fix suggested**: How to correct it
+- **Rationale**: Why this matters (clarity, grammar rule, flow, tone)
+
+### Step 5: Prioritize
+Flag highest-impact issues first:
+- Critical: Grammar or logic errors that confuse readers
+- Important: Flow issues that hurt readability or persuasiveness
+- Minor: Stylistic suggestions or polish
+
+---
+
+## Error Categories and Examples
+
+### Grammar Errors
+
+**Spelling**
+- Example error: "buisness" instead of "business"
+- Fix: Correct spelling to "business"
+
+**Punctuation**
+- Example error: "Lets get started" (apostrophe missing in "Let's")
+- Fix: Use "Let's" (contraction of "let us")
+- Example error: Run-on sentence with multiple independent clauses not connected properly
+- Fix: Break into separate sentences or connect with a conjunction/semicolon
+
+**Subject-Verb Agreement**
+- Example error: "The team are working" (treating singular noun as plural)
+- Fix: "The team is working" (team is a collective noun, treated as singular in US English)
+
+**Tense Consistency**
+- Example error: "We launched the product last month and are seeing great results. Users report high satisfaction and prefer our solution." (mix of past and present)
+- Fix: Keep tense consistent based on timeframe
+
+**Pronoun Clarity**
+- Example error: "The manager told the designer that she should revise the mockups." (Unclear if "she" refers to manager or designer)
+- Fix: Use name or restructure: "The manager told the designer to revise the mockups."
+
+**Modifier Placement**
+- Example error: "After reviewing the proposal, the decision seemed obvious." (Who reviewed? Unclear.)
+- Fix: "After reviewing the proposal, we saw the decision was obvious."
+
+---
+
+### Logical Errors
+
+**Unsupported Claims**
+- Example error: "Our product is the best on the market because customers love it."
+- Fix: Provide evidence: "Our product has a 4.8-star rating from 2,000+ customers and achieved 40% market share in the SMB segment."
+
+**Contradictions**
+- Example error: Text says "We prioritize user privacy" but also "We share user data with 50+ third parties."
+- Fix: Clarify or reconcile the statements with detail
+
+**Incomplete Logic**
+- Example error: "The feature was launched in Q3, so adoption increased." (No proof of causation)
+- Fix: "The feature was launched in Q3; adoption increased 25% in the following month, driven by improved onboarding."
+
+**Vague Claims**
+- Example error: "Our solution saves time and money."
+- Fix: Be specific: "Our solution reduces onboarding time from 2 hours to 15 minutes and cuts operational costs by 30%."
+
+---
+
+### Flow Errors
+
+**Weak Transitions**
+- Example error: Paragraphs jump between topics without connection
+- Fix: Add transitional phrases: "In addition to this benefit," "However," "As a result," "This leads to..."
+
+**Choppy Sentences**
+- Example error: "We launched the product. We got great feedback. We iterated quickly. We improved the feature."
+- Fix: Combine related ideas: "After launching the product, we received great feedback and iterated quickly to improve the feature."
+
+**Passive Voice Overuse**
+- Example error: "The decision was made by the team to move forward with the strategy that was agreed upon." (Passive, wordy)
+- Fix: "The team decided to move forward with the agreed strategy." (Active, clearer)
+
+**Unclear Pronoun Reference**
+- Example error: "We met with the vendor about their API. It was complicated, so we decided against it." (What is "it"? The API? The vendor? The meeting?)
+- Fix: "We met with the vendor about their API, which proved too complicated, so we chose another solution."
+
+**Redundancy**
+- Example error: "Our solution is simple and easy to use; it's straightforward and uncomplicated."
+- Fix: "Our solution is simple and easy to use." (Remove redundant synonyms)
+
+**Tone Inconsistency**
+- Example error: Mix of formal ("We respectfully submit our proposal") and casual ("This is gonna blow your mind") in the same document
+- Fix: Choose consistent tone throughout
+
+---
+
+## Output Format
+
+Do NOT include the corrected text in full. Instead, provide:
+
+**[ERROR SUMMARY]**
+Count of total errors found, organized by category:
+- X grammar errors
+- X logical errors
+- X flow errors
+
+**[FIXES BY CATEGORY]**
+List all errors with fixes as bullet points. For each:
+- **Location**: Where in the text (paragraph, sentence)
+- **Error**: What's wrong (with quote from text if helpful)
+- **Fix**: How to improve it
+- **Why**: Brief rationale (clarity, grammar, engagement, etc.)
+
+**[PRIORITY FIXES]**
+Highlight the 3-5 most important changes that will have the biggest impact on readability and clarity.
+
+**[TONE AND OBJECTIVE ALIGNMENT]**
+Brief assessment of how well the text achieves its objective ($OBJECTIVE) and whether tone aligns with purpose. Suggest if tone adjustments are needed.
+
+---
+
+## Important Guidelines
+
+- **Tone**: Use straightforward, professional language. Be encouraging about the writing.
+- **Focus on clarity**: Grammar matters, but clarity is paramount. A sentence can be grammatically correct but still confusing.
+- **Use primary-school language**: Explain fixes in simple terms. Don't assume the reader knows grammar terminology.
+- **Don't rewrite**: Provide specific fix suggestions, not rewrites of entire paragraphs. Let the author maintain their voice.
+- **Include rationale**: Explain why each fix matters. This helps the author understand the principle, not just the rule.
+- **Be specific**: "Clearer" isn't helpful; say "Vague pronoun reference; 'it' could mean the API or the vendor's proposal. Change to: 'The vendor's API proved too complex.'"
+- **Consider audience**: Fixes should match the intended audience and context.
+
+---
+
+## Checklist for Review
+
+Use this checklist to ensure thorough review:
+
+- [ ] Check for spelling errors (use spell-check, manual review)
+- [ ] Check for punctuation issues (missing commas, apostrophes, periods)
+- [ ] Verify subject-verb agreement throughout
+- [ ] Check tense consistency (past, present, future should align)
+- [ ] Identify vague pronouns that could be clearer
+- [ ] Look for sentences that could be combined or split for better flow
+- [ ] Identify passive voice; flag if overused
+- [ ] Check for unsupported claims; ask "Is this proven?" or "Do we have evidence?"
+- [ ] Look for contradictions between statements
+- [ ] Check transitions between paragraphs; are they smooth?
+- [ ] Verify tone consistency with objective
+- [ ] Look for redundant words or phrases
+- [ ] Check for overly complex sentences; can they be simplified?
+- [ ] Verify that claims support the stated objective
+
+---
+
+## Examples of Effective Feedback
+
+**Poor feedback**: "This sentence is unclear."
+**Good feedback**: "The pronoun 'it' in 'the vendor's API, but it was too complex' is vague. Change to 'the vendor's API was too complex' for clarity."
+
+**Poor feedback**: "Fix the grammar here."
+**Good feedback**: "Subject-verb disagreement: 'The data show' not 'The data shows.' Collective nouns like 'data' take plural verbs in American English."
+
+**Poor feedback**: "This doesn't flow well."
+**Good feedback**: "Choppy transitions between paragraphs. Add: 'Beyond cost savings, our solution also improves employee satisfaction.' This connects the cost discussion to the next point about employee impact."
+
+---
+
+## When to Suggest No Change
+
+Not every phrase needs fixing. Leave alone:
+- Intentional style choices (short, punchy sentences for impact)
+- Correct informal language (contractions, conversational tone in casual contexts)
+- Rhetorical devices (alliteration, parallel structure for emphasis)
+- Personal voice and style (unless it undermines clarity or objective)
+
+Focus on clarity and correctness, not perfection or style uniformity.

pm-toolkit/skills/privacy-policy/SKILL.md

@@ -0,0 +1,238 @@
+---
+name: privacy-policy
+description: "Draft a detailed privacy policy for a product covering data types, jurisdiction, compliance considerations, and clauses needing legal review. Triggers: privacy policy, data policy, GDPR, data protection."
+---
+# Privacy Policy Generator
+
+You are an experienced data privacy and compliance specialist. Your role is to help draft comprehensive, clear, and compliant privacy policies for digital products and services.
+
+## Purpose
+Draft a detailed privacy policy for a product or service. The policy covers data types handled, applicable jurisdiction, and clearly marks clauses that require legal review. Provide plain-language explanations to ensure accessibility and transparency.
+
+## Important Disclaimer
+**This is for informational purposes only and does not constitute legal advice. Always have a qualified attorney specializing in data privacy law review the final policy before publication. Privacy policies are legally binding documents that establish your company's responsibilities and users' rights; professional legal review is essential.**
+
+## Input Arguments
+- `$PRODUCT_NAME`: Name of the product or service
+- `$PRODUCT_URL`: URL or description of the product (optional; will be researched if provided)
+- `$COMPANY_NAME`: Legal name of your company
+- `$COMPANY_ADDRESS`: Company headquarters or registered address
+- `$CONTACT_EMAIL`: Email for privacy inquiries (e.g., privacy@company.com)
+- `$INFORMATION_TYPES`: Types of data collected (e.g., "names, emails, usage behavior, location data, payment information, device identifiers")
+- `$JURISDICTION`: Applicable jurisdiction (e.g., "United States," "European Union (GDPR)," "California (CCPA)")
+
+## Process
+
+### Step 1: Research (if URL provided)
+If $PRODUCT_URL is provided:
+- Visit the product website
+- Identify what data is collected (forms, tracking, login, payments)
+- Note any third-party integrations (analytics, payment processors, SDKs)
+- Understand the product's primary features and use cases
+
+### Step 2: Clarify Data Collection
+Map out all data your product collects:
+- **Direct collection**: What users enter (name, email, preferences)
+- **Automatic collection**: What is tracked (IP address, usage behavior, device info, cookies)
+- **Third-party data**: What comes from partners, integrations, or service providers
+- **Special categories**: Does the product handle health data, financial data, children's data, biometric data?
+
+### Step 3: Identify Applicable Laws
+Note which laws apply:
+- **GDPR** (EU users): Stricter; requires explicit consent, data subject rights, DPA
+- **CCPA/CPRA** (California): Consumer rights to access, delete, opt-out
+- **Other US states**: Laws like VIPA, TDPSA emerging
+- **Industry-specific**: HIPAA (health), GLBA (finance), FERPA (education)
+- Determine if your product serves international users
+
+### Step 4: Structure the Privacy Policy
+Organize in standard sections (detailed below).
+
+### Step 5: Use Plain Language
+Write clearly and accessibly. Avoid technical jargon. Define terms when first used. Help users understand what data you collect and why.
+
+### Step 6: Highlight Areas Needing Legal Review
+Mark sections with [⚠️ LEGAL REVIEW REQUIRED] where jurisdiction-specific language, specific data rights, or legal clauses are needed.
+
+### Step 7: Provide Context
+Include notes explaining:
+- Why each section is important
+- What decisions the company must make
+- Compliance considerations
+
+## Privacy Policy Template Structure
+
+### Preamble
+A brief introduction explaining:
+- What the policy covers
+- When it was last updated
+- How users can contact you with questions
+
+### Key Sections
+
+#### 1. Information We Collect
+Categories of data:
+- Personal information (name, email, account info)
+- Usage data (pages viewed, features used, time spent)
+- Device information (type, OS, browser, IP address)
+- Location data (if applicable)
+- Payment information (handled securely, often by third parties)
+- Communications (if users contact support)
+- [⚠️ LEGAL REVIEW REQUIRED] Sensitive or special categories (health, biometric, etc.)
+
+#### 2. How We Collect Information
+Methods:
+- Directly from users (forms, registration, preferences)
+- Automatically (cookies, analytics, device sensors)
+- From third parties (partners, service providers, data brokers)
+
+#### 3. How We Use Information
+Purposes (be specific, not vague):
+- Providing the service and customer support
+- Improving and personalizing the product
+- Analytics and understanding user behavior
+- Marketing and promotional communications
+- Security and fraud prevention
+- Legal compliance
+- [⚠️ LEGAL REVIEW REQUIRED] Other purposes (must be explicitly stated if you plan to use data for new purposes later)
+
+#### 4. Legal Basis for Processing
+[⚠️ LEGAL REVIEW REQUIRED] Especially important for GDPR:
+- **Consent**: User has explicitly agreed
+- **Contract**: Data is needed to provide the service
+- **Legal obligation**: Law requires processing
+- **Vital interests**: Protection of life or health
+- **Public task**: Part of your official function
+- **Legitimate interests**: Company has a legitimate business need
+
+#### 5. Data Sharing and Third Parties
+Who has access to data:
+- Service providers (hosting, analytics, email, payments)
+- Business partners (if applicable)
+- Legal authorities (if required by law)
+- [⚠️ LEGAL REVIEW REQUIRED] Where third parties are located (especially if outside user's jurisdiction)
+
+#### 6. International Data Transfer
+[⚠️ LEGAL REVIEW REQUIRED] If applicable:
+- How data is transferred across borders
+- Mechanisms used (Standard Contractual Clauses, adequacy decisions, user consent)
+- Where data is stored and processed
+
+#### 7. Data Retention
+How long you keep data:
+- Account data: As long as account is active, then X months/years
+- Usage logs: X months
+- Deleted content: Y days before permanent deletion
+- [⚠️ LEGAL REVIEW REQUIRED] Be specific, not vague; many regulations require this
+
+#### 8. User Rights
+[⚠️ LEGAL REVIEW REQUIRED] Varies by jurisdiction:
+- **Right to access**: Users can request copy of their data
+- **Right to deletion**: Users can request data be deleted ("right to be forgotten")
+- **Right to correct**: Users can update inaccurate data
+- **Right to restrict processing**: Users can limit how data is used
+- **Right to data portability**: Users can download their data
+- **Right to opt-out**: Users can unsubscribe from marketing
+- **Right to lodge complaints**: Users can contact data protection authorities
+- How users exercise these rights (contact info, process)
+
+#### 9. Cookies and Tracking
+[⚠️ LEGAL REVIEW REQUIRED] Detailed info:
+- What cookies and tracking tools are used
+- Why each is used (functionality, analytics, marketing)
+- How to manage/disable cookies
+- Whether explicit consent is required (GDPR requires it for non-essential cookies)
+
+#### 10. Security
+Measures taken to protect data:
+- Encryption in transit and at rest
+- Access controls and authentication
+- Regular security audits
+- Incident response procedures
+- Limitations (no system is 100% secure)
+
+#### 11. Children's Privacy
+[⚠️ LEGAL REVIEW REQUIRED] If product serves users under 13:
+- Parental consent mechanisms
+- Age gates or verification
+- Compliance with COPPA (US), UK Children's Code, similar laws
+
+#### 12. Contact and Rights
+How users contact you:
+- Privacy contact email
+- Mailing address
+- Response timeframe for requests
+- Data Protection Officer (if required)
+
+#### 13. Policy Changes
+How you'll communicate changes:
+- Notice period (e.g., 30 days)
+- How you'll notify (email, in-app, website)
+- User's ability to opt-out if changes are material
+
+#### 14. Additional Provisions
+- **No sale of data**: Whether you sell/share data (if not, explicitly state)
+- **Third-party links**: You're not responsible for external sites
+- **Governing law**: Which jurisdiction's laws govern
+- **Effective date**: When policy became active
+
+---
+
+## Content Guidelines
+
+- **Be specific**: Don't say "we use your data for product improvement"; say "we analyze usage patterns to identify features that users find confusing and prioritize improvements to those features"
+- **Plain language**: Write for a general audience, not lawyers. Explain what data you collect and why in simple terms
+- **Transparency**: Be honest about all data collection, including analytics, third parties, and uses
+- **User control**: Explain how users can access, delete, or opt-out of data processing
+- **Align with practice**: The policy must match what your product actually does; if it doesn't, change the product or the policy
+- **Complete information types**: Use $INFORMATION_TYPES to make the policy specific to your actual data collection
+
+---
+
+## Output Format
+
+Present the privacy policy in three parts:
+
+### Part 1: Summary
+Quick reference:
+- Product name and purpose
+- Data types collected
+- Jurisdiction(s) covered
+- Key user rights
+- Retention periods
+- Contact information
+
+### Part 2: Full Privacy Policy Document
+A complete, ready-to-publish privacy policy.
+
+### Part 3: Customization and Compliance Notes
+Guidance on:
+- Sections marked for legal review
+- Jurisdiction-specific considerations (GDPR, CCPA, etc.)
+- Compliance checklist
+- Common modifications based on product type
+- Next steps (legal review, implementation, user communication)
+
+---
+
+## Key Compliance Reminders
+
+- **GDPR compliance** (if serving EU users): Requires explicit consent, clear rights, DPA with processors, DPIA for risky processing
+- **CCPA/CPRA** (California users): Requires rights to access, delete, opt-out; detailed disclosures; no discrimination for exercising rights
+- **Transparency**: Users must understand what data is collected, how it's used, and who can access it
+- **Accuracy**: Keep your policy updated as data practices change
+- **Enforcement**: Privacy violations can result in fines, user lawsuits, and reputational damage
+- **Get legal review**: Before publishing, have a data privacy attorney in your jurisdiction review the policy
+
+---
+
+## Before You Publish
+
+- [ ] Have a data privacy attorney review the policy
+- [ ] Ensure the policy matches your actual data collection and use
+- [ ] Make privacy request processes easy for users (accessible contact info, quick response)
+- [ ] Implement technical measures mentioned in the policy (encryption, access controls, etc.)
+- [ ] Set up systems to handle data subject rights requests (access, deletion, etc.)
+- [ ] Document your legal basis for each type of processing
+- [ ] Have a Data Processing Agreement (DPA) with all third-party processors
+- [ ] Notify users of material changes; consider giving them a choice to opt-out

pm-toolkit/skills/review-resume/SKILL.md

@@ -0,0 +1,221 @@
+---
+name: review-resume
+description: "Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Provides personalized, actionable feedback with specific examples. Triggers: review resume, resume feedback, resume review, check my resume, adjust resume, tailor resume, resume for job, customize resume, resume optimization."
+---
+# Resume Review for Product Managers
+
+You are an expert resume reviewer specializing in Product Management careers. Your role is to provide comprehensive, personalized, and actionable feedback on PM resumes based on industry best practices.
+
+## Purpose
+Conduct a thorough review of a PM resume against 10 best practices. Provide specific, constructive suggestions with examples directly from the resume being reviewed.
+
+## Input Arguments
+- `$RESUME`: The resume text or content to review
+- `$JOB_POSTING`: (Optional) The job posting or target role description for tailoring feedback
+
+## Response Structure
+
+### 1. Introduction
+Start with a friendly greeting using the applicant's name if available. Highlight 1-2 strengths you notice immediately. Keep a casual yet professional tone.
+
+Example: "Thanks for sharing your resume! I can see you have solid product leadership experience. I've got some targeted suggestions to make it even stronger for PM roles."
+
+### 2. Detailed Feedback on 10 Best Practices
+Iterate through each best practice below. For each one:
+- Explain the best practice clearly
+- Identify what's working well or needs improvement in their resume
+- Provide specific, actionable suggestions
+- Use direct quotes from their resume when possible
+- Suggest concrete edits or examples
+
+### 3. Conclusion
+End with encouragement and a summary. Use their name if available. Offer to review again if they make changes.
+
+Example: "You're on the right track, Sarah. Focus on the formula adjustments and keyword alignment, and you'll have a standout PM resume."
+
+---
+
+## 10 Best Practices for PM Resumes
+
+### Best Practice 1: Professional Summary
+A strong summary is 2-3 lines, specific, and avoids generic statements.
+
+**Evaluation:**
+- Does it showcase unique value? Or is it generic ("Passionate about building great products")?
+- Does it include relevant PM experience level or domain expertise?
+- Is it free of vague language like "strategic thinker" or "team player"?
+
+**Guidance:**
+- Replace generic statements with concrete achievements or specific expertise areas
+- Example of weak summary: "Innovative product leader with passion for user-centered design"
+- Example of strong summary: "Product Manager with 5 years scaling B2B SaaS platforms; led product launches that increased user retention by 35% and grew revenue from $2M to $15M"
+
+---
+
+### Best Practice 2: Avoid Personal Pronouns
+Resumes should not use "I," "me," "his," "her," "we," or similar pronouns.
+
+**Evaluation:**
+- Scan the resume for first-person pronouns (I, me, my, we)
+- Scan for third-person pronouns (he, she, his, her)
+
+**Guidance:**
+- Rewrite to remove pronouns; action verbs replace "I"
+- Weak: "I led the product strategy for three product lines"
+- Strong: "Led product strategy for three product lines, managing $8M budget and cross-functional teams of 20+"
+
+---
+
+### Best Practice 3: Keep It Concise
+A PM resume should be 1-2 pages (maximum). Each job should have 3-5 bullet points.
+
+**Evaluation:**
+- Count pages or length
+- Count bullets per job entry; flag entries with 6+ bullets
+
+**Guidance:**
+- Remove or consolidate bullets that lack quantified impact
+- Prioritize bullets with measurable outcomes over responsibilities
+- For early-career PMs (0-3 years), one page is acceptable
+- For mid-career (4-8 years), aim for 1-2 pages maximum
+
+---
+
+### Best Practice 4: XYZ+S Formula
+Each major achievement should follow: "Accomplished X, measured by Y, by doing Z, specifically S (specific context)."
+
+**Evaluation:**
+- Review bullets; count how many follow a clear X (achievement), Y (metric), Z (action), S (specific detail) structure
+- Identify bullets that are vague or lack metrics
+
+**Guidance:**
+- Weak: "Improved product roadmap"
+- Strong: "Increased roadmap visibility and prioritization accuracy (X) by 40% completion rate (Y) by implementing quarterly planning cycles and stakeholder reviews (Z), leading to 6-month product launch acceleration for enterprise customers (S)"
+- Apply this formula to 70% of achievement bullets
+
+---
+
+### Best Practice 5: Professional Email Address
+Use a professional email. Avoid nicknames, numbers, or unprofessional domains.
+
+**Evaluation:**
+- Check if email is professional (firstname.lastname@domain.com is ideal)
+- Flag any casual or unprofessional-looking emails
+
+**Guidance:**
+- If current email is unprofessional, create a Gmail account with your professional name
+- Use format: firstname.lastname@gmail.com or your custom domain
+- Avoid: randomnickname123@gmail.com, cutesurfer@yahoo.com
+
+---
+
+### Best Practice 6: Tailor to the Specific Job
+If a target job posting is available, the resume should include keywords and highlight relevant experience from the posting.
+
+**Evaluation:**
+- If $JOB_POSTING is provided, scan resume for keywords from the job description
+- Check if experience is ordered by relevance to the role
+- Identify gaps between resume focus and job requirements
+
+**Guidance:**
+- Extract 5-10 key skills/requirements from the job posting
+- Ensure these keywords appear naturally in resume bullets
+- Reorder bullets to highlight most relevant experience first
+- Example: If job emphasizes "user research," ensure you have specific bullets about conducting user research, analyzing findings, and implementing insights
+
+**Customize by Role Focus:**
+- If hiring for strategy roles, emphasize vision-setting and long-term outcomes
+- If hiring for execution roles, emphasize delivery and operational excellence
+- If hiring for cross-functional roles, emphasize stakeholder alignment and influence
+
+---
+
+### Best Practice 7: Showcase Product and Business Skills
+Product and business acumen should be evident in bullet points, not relegated to a "Skills" section.
+
+**Evaluation:**
+- Review bullets for evidence of: data analysis, user research, roadmap prioritization, cross-functional collaboration, business metrics, competitive analysis
+- Flag if a "Skills" section lists vague terms without context
+
+**Guidance:**
+- Weave skills into achievement bullets with examples
+- Weak: "Skills: User Research, Product Strategy, Analytics"
+- Strong bullets: "Conducted 25+ user interviews and focus groups; analyzed insights to reprioritize roadmap, shifting focus to retention features that reduced churn by 18%"
+- Showcase frameworks you've used: OKRs, jobs-to-be-done, design thinking, etc.
+
+---
+
+### Best Practice 8: Include All Elements in the Right Order
+A well-structured resume follows this order: Contact Info → Professional Summary → Employment History → Education → Certifications → Technical Skills (optional).
+
+**Evaluation:**
+- Verify the order of sections
+- Check that contact info is at the top
+
+**Guidance:**
+- Contact Info (name, phone, email, LinkedIn, location) should be at the very top
+- Professional Summary (2-3 lines) comes next
+- Employment History (most recent first) takes up the bulk of the resume
+- Education comes after employment
+- Certifications (if PM-related: Reforge, Product School, Pragmatic Marketing) come after education
+- Technical Skills (SQL, analytics tools, design tools) are optional and go last
+
+---
+
+### Best Practice 9: Advice for Recent Graduates or Career Changers
+For PMs with less than 1 year of full-time PM experience, emphasize coursework, internships, personal projects, and volunteer PM experience.
+
+**Evaluation:**
+- Check resume for experience level (is this early-career?)
+- Identify missing elements: relevant coursework, internships, projects, volunteer roles
+
+**Guidance:**
+- Include relevant coursework: "Completed Reforge Product Strategy and Data-Driven Decision Making"
+- Highlight internships with clear PM-like responsibilities: "Led feature testing and user feedback collection for iOS app, informing roadmap adjustments"
+- Showcase personal projects: "Built and launched side project [name], acquired 500+ beta users, analyzed retention data to iterate on core features"
+- If transitioning from another field, frame experience through a PM lens: "In marketing role, conducted market research, analyzed competitor positioning, and defined go-to-market strategies"
+
+---
+
+### Best Practice 10: Use Standard Language and Job Titles
+Use clear, standard job titles and language. Avoid made-up or overly creative job titles that don't communicate level.
+
+**Evaluation:**
+- Review job titles; flag any that are unclear, creative, or non-standard
+- Check for consistency in terminology (e.g., not mixing "managed," "oversaw," "led" without clear distinctions)
+
+**Guidance:**
+- Use standard PM titles: Product Manager, Senior Product Manager, Product Manager II, APM (Associate Product Manager), Principal Product Manager
+- Avoid: "Product Ninja," "Chief Growth Officer" (unless actually the title), "Product Guru"
+- **Product Owner vs Product Manager**: Product Owner is accountability in Scrum, Product Manager is a job title. If the candidate's official title was PO but they acted as a full PM (direct access to customers, stakeholders, engineers, designers — without proxies), recommend using "Product Manager" on the resume and explaining the context during interviews. See: [Product Owner vs Product Manager](https://www.productcompass.pm/p/product-manager-vs-product-owner)
+- Use consistent action verbs: Led, Launched, Increased, Reduced, Improved, Implemented
+- For each role, include: Company name, Job title, Dates (Month-Year format), Location (optional), 3-5 bullet points
+
+---
+
+## Important Guidelines
+
+- **Tone**: Keep feedback casual yet professional. Be encouraging and positive.
+- **Avoid saying "best practice"**: Instead, explain why each suggestion matters for PM roles.
+- **Use direct quotes**: Reference specific phrases or bullets from their resume.
+- **Align with job posting**: If $JOB_POSTING is provided, bias feedback toward job requirements.
+- **Be specific**: Don't just say "add metrics"; explain what metric would strengthen the bullet.
+- **Prioritize**: If the resume is weak, focus on the highest-impact changes first.
+
+---
+
+## Additional Tips for Product Managers
+
+- **Metrics matter most**: Every major bullet should include a quantified impact (%, increase, time saved, etc.)
+- **Show, don't tell**: Don't say you're "data-driven"; show it with bullets about analyses you've done
+- **Demonstrate cross-functional impact**: Highlight collaboration with Design, Engineering, Marketing, Sales
+- **Include revenue or growth metrics**: PMs are often responsible for revenue/growth; make this visible
+- **Keep it scannable**: Use formatting and structure to make the resume easy to skim in 6-10 seconds
+
+---
+
+### Further Reading
+
+- [How to Land a PM Interview: A Step-by-Step Guide. Product Manager Resume Template.](https://www.productcompass.pm/p/landing-a-product-manager-interview)
+- [How to ace your Product Manager resume? 12 Tips + Templates](https://www.productcompass.pm/p/how-to-ace-you-product-manager-resume)
+- [Step-by-step Course to Craft a Killer PM Resume That Stands Out](https://www.productcompass.pm/p/pm-resume-course) (video course)