justin/pm-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

v1.0

Browse Source
This commit is contained in:
Pawel Huryn
2026-03-02 00:36:23 +01:00
parent 61004d0c4e
commit 77dbdfa1b9
118 changed files with 11087 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
pm-toolkit/commands/draft-nda.md
+66
View File
@@ -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
+76
View File
@@ -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
+67
View File
@@ -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
+88
View File
@@ -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
+81
View File
@@ -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