Battlecard Memory

Draft and update competitor battlecards as files, and persist durable competitor learnings to memory so future work starts from accurate, current intelligence.

When to use

• A rep or stakeholder asks for a battlecard on a named competitor.
• New competitor information surfaces (pricing change, feature launch, positioning shift) and needs to be captured.
• An existing battlecard needs refreshing with newer facts before a deal or campaign.
• You need to recall prior competitor findings before drafting new content.

Tools

• read-file — open an existing battlecard or prior notes file before updating it, so edits build on the current version instead of overwriting it blind.
• write-file — create or update the battlecard artifact (competitor overview, strengths/weaknesses, pricing, objection handling, positioning).
• update-memory — persist durable, reusable competitor facts (pricing tiers, key differentiators, known weaknesses, past win/loss reasons) so they survive beyond a single task.

Playbook

1. Clarify which competitor and which battlecard sections are needed (overview, pricing, objection handling, feature comparison).
2. Check for an existing battlecard file and read-file it to see what is already documented.
3. If no file exists, draft a new battlecard structure covering: company overview, target segment, pricing, strengths, weaknesses, common objections and responses, and recent news.
4. Incorporate any new information provided in the task or already known from memory into the draft.
5. write-file the updated or new battlecard to a clearly named file so it is easy to find next time.
6. Extract the durable facts from this update (pricing, differentiators, weaknesses, win/loss patterns) and update-memory with each one, keeping entries concise and dated where relevant.
7. If the update reveals information that will go stale quickly (e.g. a promotional price), note that explicitly in the battlecard file so future readers know to verify it.
8. Re-read-file the final saved battlecard to confirm the write succeeded and the content is complete and well-formed.
9. Summarize what was added or changed in the battlecard and what was persisted to memory.

Failure modes

• File not found or path wrong when calling read-file -> treat as no prior battlecard, start fresh, and note in the new file that no prior version existed.
• write-file fails or content looks truncated -> retry once with the full content; if it still fails, stop and report the issue rather than claiming the battlecard was saved.
• Conflicting information between the task input and what memory already holds -> prefer the newer, more specific source, but update-memory with a note flagging the correction rather than silently overwriting.
• Information is speculative or unverified -> label it clearly as unverified in the battlecard and do not persist it to memory until confirmed.

Done when

• A battlecard file exists (or is updated) via write-file with current, well-structured competitor information.
• Durable competitor facts from this session have been captured via update-memory.
• The final battlecard has been confirmed readable via read-file and a summary of changes has been provided.