Skip to main content

write-a-positioning-statement

Write and test a positioning statement grounded in audience evidence and credible difference. Use when a product, service, project, or program needs a clear category, value, alternative, and proof.

Informações da origem

Repositório
protosphinx/sphinxstack
Última atividade na origem
29 de julho de 2026 às 13:55
Idioma detectado do SKILL.md
inglês
Estrelas
3
Forks
0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
2 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
name
write-a-positioning-statement
category
write
description
Write and test a positioning statement grounded in audience evidence and credible difference. Use when a product, service, project, or program needs a clear category, value, alternative, and proof.
# write-a-positioning-statement Make a strategic choice about who this is for and why it matters. The internal statement can be plain; it is not automatically public copy. ## Procedure 1. Gather the audience definition, problem evidence, product behavior, alternatives, constraints, and proof. 2. Name the specific situation and audience whose choice the positioning should influence. 3. Describe the category or frame the audience already understands. 4. State the valuable outcome in audience language, not a list of features. 5. Identify the real alternative, including manual work, delay, or doing nothing. 6. Select a difference the product can sustain and evidence. 7. Draft: `For [audience in situation], [offering] is the [category] that [value], unlike [alternative], because [credible proof].` 8. Challenge every phrase for ambiguity, exclusion, unsupported superiority, and competitive imitation. 9. Test comprehension and relevance with representative people without coaching them. 10. Record the approved version, proof dependencies, audiences not served, and review triggers. ## Guardrails - Do not use “best,” “only,” or outcome claims without current support. - Avoid defining the audience only by age, title, or aspiration. - Keep future roadmap items out of present-tense proof. - Route regulated, comparative, financial, health, or environmental claims through authorized review. ## Done - The positioning statement names audience, situation, category, value, alternative, and proof - Evidence verifies the chosen difference - Representative readers can explain the intended meaning accurately - Unsupported claims and excluded audiences are recorded
Ver no GitHub