From pm-sales
Create a competitive sales battlecard for any competitor. Use when asked to build a battlecard, competitive comparison, sales cheat sheet, or objection handling guide for a specific competitor. Produces a one-page battlecard with positioning, differentiators, objection responses, and landmines.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-sales:sales-battlecardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produces a practical one-page competitive battlecard that sales reps can use in calls — not a theoretical analysis.
Produces a practical one-page competitive battlecard that sales reps can use in calls — not a theoretical analysis.
Updated: [Date] — Review quarterly
When a prospect mentions [Competitor], say: "[Your positioning in one sentence]"
(Be honest about their genuine strengths)
(Specific differentiators with proof points)
"[Competitor] is cheaper" "You are right their list price is lower. What our customers find is [specific TCO difference]. [Customer] saw [result]. Should we explore total cost of ownership?"
"We already use [Competitor]" "That is helpful. What is working well? [Listen] And what is one thing you wish was better?"
"[Competitor] has [feature] you do not" "You are right. What problem are you solving with that feature? [Listen] Here is how our customers solve that..."
We win when: [Scenario — e.g. customer prioritises outcome over price] We lose when: [Honest scenario — e.g. primary driver is lowest upfront cost]
npx claudepluginhub mileadev/pm-claude-skills --plugin pm-salesGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
2plugins reuse this skill
First indexed Jul 8, 2026