| name | positioning-claim-map |
|---|---|
| description | Use when you need positioning claim map to map competitors, alternatives, claims, proof, objections, and whitespace. |
- Produce positioning claim map.
- Read
references/pattern.mdbefore drafting; it contains product mechanics, required inputs, decision rules, artifact fields, QA checks, failure modes, proof metrics, and an example prompt.
- Anchor the artifact around these fields: alternative, claim, proof, objection.
- Use the artifact to decide: Which message, segment, or channel assumption changes.
- Do not mark ready until: Observed evidence, synthesis, and recommendation are labeled separately.
- Confirm the requested artifact, target audience, and review owner.
- Gather only the missing high-risk inputs; infer low-risk defaults and label assumptions.
- Apply the relevant decision rules and artifact template from
references/pattern.md. - Return the artifact with QA checks, failure modes, proof metric, and next action.
Return positioning claim map. Include the decision supported, required inputs, generated artifact, QA checks, failure modes, proof metric, and next action.
Use another skill if the final artifact is not positioning claim map, the main decision is outside customer-research-synthesis, or the user only needs broad strategy.
- Keep private evidence identities and unpublished links out of repo-facing output.
- Separate observed evidence, inference, and recommended action.
- Ask for missing high-risk inputs before producing launch-ready work.
- Keep the artifact narrow enough to execute or review today.