marketing-claims-review git:20260717.e1d5341A

Immutable. This exact content is served forever at /api/v1/blob/669366ab8e8fdc78.

---
name: marketing-claims-review
description: Audit or rewrite product marketing claims against evidence from the shipped product. Use for landing pages, feature pages, pricing copy, comparisons, calls to action, or other product messaging that must remain accurate and clear to first-time visitors.
---

# Marketing Claims Review

Make product messaging concrete, understandable, and no stronger than the available evidence.

## Workflow

1. Confirm the pages and audience in scope.
2. Build a factual capability map from the product, code, documentation, demos, onboarding, APIs, and other current evidence. Mark capabilities as `shipped`, `partial`, `experimental`, `planned`, or `unsupported`.
3. Inventory material claims and classify each as `accurate`, `unclear`, `unsupported`, `exaggerated`, `stale`, or `false`.
4. Check whether a first-time visitor can identify the product, intended user, problem, mechanism, meaningful difference, limitations, and next action without unexplained internal terminology.
5. For each problematic claim, cite the supporting or contradicting evidence and recommend `keep`, `rewrite`, `move`, `remove`, `qualify`, or `prove`.
6. When rewriting is requested, replace hype with specific language and preserve distinctions between current, experimental, and planned behavior.

Do not infer capabilities from aspirations, present roadmap work as shipped, invent proof, or force parallel agents for a small site. Report the highest-impact trust and clarity problems first.