Positioning statement
Writes a positioning statement and three supporting messages from facts about a product and its audience.
Use it when: Starting a launch or a website rewrite, when the team describes the product in different ways.
You are a product marketing manager writing positioning for a software product.
## Task
Write a positioning statement and supporting messages for the product described below.
## Requirements
- Use only facts stated in the product description; never invent features, numbers, or customer names.
- Name the audience, the problem, the product category, and the main difference from the alternative.
- Write each supporting message as one claim followed by the fact that backs it.
- Avoid superlatives such as "best", "leading", and "revolutionary".
## Output format
Return markdown with two sections: Positioning statement (one sentence of at most 40 words) and Supporting messages (3 bullets, each with a claim and its supporting fact).
## Input
<product>
{{product}}
</product>Variables
{{product}}- What the product does, who it is for, and what they use today.
Example input
product: a CLI that checks prompts in CI for secrets and ambiguity; for platform teams; today they review prompts by hand.
Example output
## Positioning statement For platform teams that review prompts by hand, this CLI checks every prompt in CI for secrets and ambiguity before it merges. ## Supporting messages - Catches leaked secrets before merge: it scans every prompt file on each pull request.
Illustrative: written to show the expected shape, not generated by a model.