メニュー
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.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/TuYv/ccpm --skill battle-card-builderコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data. Not for campaign structure design — use campaign-architect; not for creative production — use ad-creative-builder. 付费广告账户审计/ROAS评分
Use when the user asks to "write ad copy", "generate RSA headlines", or "build ad creative at volume"; produces ad units — RSA headlines/descriptions, hooks, and an angle matrix — message-matched to the destination landing page. Not for scoring an ad account — use ad-account-auditor; not for the post-click page — use landing-optimizer; not for organic articles — use content-writer. 广告创意/广告文案/RSA标题
Use when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"; produces a hypothesis, variant matrix, sample-size/duration/power plan, and a documented effect/uncertainty read from own exported results. It applies only a precommitted owner-approved action rule; the statistical helper never chooses a business action. Not for producing variants — use ad-creative-builder; not for reading back one shipped change — use paid-measurement-loop. 广告AB测试设计/实验设计/显著性判定/增效测试
SOC 職業分類に基づく
SKILL.md を表示中
| name | battle-card-builder |
| argument-hint | [your product vs which competitor, and the deal context] |
| 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. |
| intent | Autonomous battle card construction: given your product and one competitor, the AI does the fieldwork — pricing pages, reviews, release notes, customer stories — and produces a field-action card with a source URL and Fact/Inference/Assumption label on every claim, sized to a rep's thirty seconds. |
| type | workflow |
| theme | market-intelligence |
| best_for | ["Arming sales against one competitor with claims they can actually defend","Turning a competitive snapshot or watch report into a field-action artifact","Building trap questions whose documented answers favor you"] |
| scenarios | ["We keep hitting the same rival in enterprise deals — build the battle card from public evidence","Our battle card is six months old and sales stopped trusting it; rebuild it with sources"] |
| estimated_time | 20-35 min per run |
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.
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 or
competitive-intel-watch 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."
autonomous-investigation
contract — question budget of 3, search-plan gate, Fact/Inference/Assumption labels, Just Enough
Mode, stable schema, 4-option Final Step.intelligence-collection-disciplines.# Battle Card: [Your Product] vs [Competitor]
**As-of date:** | **Deal context:** [segment, buyer]
## 1. Thirty-Second Read
- **They win when:** [1-2 bullets, labeled]
- **We win when:** [1-2 bullets, labeled]
- **The one thing to say:** [a single defensible sentence]
## 2. Say This
- [Talking point] — [evidence: URL, date, label]
- [Max 4; every one sourced]
## 3. Ask This (trap questions)
- "[Question whose documented answer favors us]" — [the documented answer: URL, label]
- [Max 3; never ask what you cannot evidence]
## 4. Watch Out For
- [Their strength a rep should not walk into] — [URL, label]
- [Their likely counter to our pitch] — [Inference, basis]
## 5. Pricing & Packaging Snapshot
- [Their tiers/pricing as published] — [URL, as-of date]
- [Where "contact sales" hides the number] — [labeled]
## 6. Do Not Say
- [Claims we cannot evidence, or that invite a counter]
## Appendix: Evidence Table
| Claim | Label | Source | Date |
|---|---|---|---|
### Assumptions to Validate
- [Assumption 1] / [Assumption 2] / [Assumption 3]
A copy/paste fill-in version of this schema, with quality checks, lives in template.md.
competitive-intel-watch to keep this card currentAccept 1, 2, 3, 4, 1 and 3, Verbose Mode, or a custom path.
A trap question built correctly (fictional):
Ask this: "How does your migration handle custom fields over the 200-field limit?" — documented answer: their own docs state custom-field migration caps at 200 with manual re-entry beyond it — Fact (docs page, checked Jul 2026). Safe to ask: the answer is in their documentation, so the rep isn't bluffing — they're citing.
A "Do Not Say" entry earning its keep:
- Don't say "they can't do SSO on the starter tier" — they shipped it in June (release notes); a rep repeating our old card walks into a correction that costs the room's trust.
- Don't lead with "we're cheaper" — true only below 50 seats (their pricing, ours); above that the math flips, and enterprise buyers check.
See examples/sample.md for a complete worked card (fictional FSM-software
market) rebuilt from the competitive-intel-watch example's update flags — the full chain landing
in a field artifact. examples/sample-industrial.md builds the
industrial version, where the channel partner is a card audience and pricing is opaque.
autonomous-investigation (Workflow) — the governing protocolintelligence-collection-disciplines (Component) — discipline sources; SIGINT keeps this card freshcompetitive-research-snapshot (Workflow) — upstream evidence basecompetitive-intel-watch (Workflow) — flags when this card's sections go stalepositioning-statement (Component) — the strategic layer the card's talking points should agree withmarket-intelligence/battle-card-builder-prompt.md in the
https://github.com/deanpeters/product-manager-prompts repo.