# Battle Card Builder

Research and draft a competitive battle card from public evidence, every claim labeled...

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Writing
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill battle-card-builder -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Research and draft a competitive battle card from public evidence, every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Battle Card Builder

## Purpose

Build a field-action competitive battle card from public evidence: **use or gather evidence → search
plan (if gathering) → draft card with per-claim labels → appendix → next-step options.** A battle
card is the artifact a rep opens mid-deal, not a research report, it must fit thirty seconds, every
claim must survive being said out loud to a hostile audience, and every claim therefore carries a
source URL, a date, and a Fact/Inference/Assumption label. Most battle cards in the wild are unlabeled
inference; this skill exists because of what it costs a rep when one of those turns out wrong.

## Input

**Works best with:** your product and its primary differentiation, and **the one competitor** this
card targets.
**Also useful:** the deal context (segment, buyer, common objections or the loss reason that triggered
this card), and any [`competitive-research-snapshot`](../competitive-research-snapshot/SKILL.md) or
[`competitive-intel-watch`](../competitive-intel-watch/SKILL.md) output in session, the skill uses
existing evidence and searches only for gaps and anything older than one quarter.

Input supplied inline with the invocation, text after the skill name, a pasted context dump, or an
appended `ARGUMENTS:` line, counts as answers already given. Use it against the question budget;
don't re-ask.

**Arriving empty-handed? That works too.** The skill opens with at most 3 questions (product +
competitor, segment + buyer, triggering objection) and proceeds on labeled assumptions if they go
unanswered.

**Example invocation:** `Build a battle card: our workflow platform vs [Competitor A], mid-market ops
buyers, triggered by three straight losses on "their integrations are deeper."`

## Key Concepts

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/battle-card-builder/SKILL.md