intended-vs-implemente…
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they…
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'
$ npx -y skills add phuryn/pm-skills --skill competitive-battlecard --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/competitive-battlecardContext preview
The summary Claude sees to decide when to auto-load this skill.
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'
name: competitive-battlecard description: "Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'"
Create a concise, sales-ready battlecard for use against a specific competitor.
You are creating a competitive battlecard for **$ARGUMENTS**.
Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first.
1. **Research the competitor** (use web search):
2. **Create the battlecard** with these sections:
| Capability | Us | Them | Winner | |---|---|---|---| | [Feature area 1] | [Our approach] | [Their approach] | [Us/Them/Tie] | | [Feature area 2] | ... | ... | ... | | Pricing | ... | ... | ... | | Support | ... | ... | ... |
| Prospect Says | Respond With | |---|---| | "Competitor X has [feature]" | "[Our alternative approach and why it's better for them]" | | "They're cheaper" | "[Value framing: total cost of ownership, ROI, hidden costs]" | | "They're more established" | "[Our advantages: speed, innovation, focus, support]" |
Questions to ask the prospect that highlight competitor weaknesses:
3. **Keep it scannable**: Sales reps need to reference this during calls. Use tables, bold text, and short bullets.
Save as markdown. Format for easy printing or sharing in Notion/Confluence.
---
68 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
Repo: phuryn/pm-skills
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they…
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission…
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating…
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by…
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded…
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team…