Skill Featured

Generate Concise Positioning Statements

Forces a team through a structured positioning exercise to produce an honest, sub-30-word competitive positioning statement.


72
Spark score
out of 100
Status Official
Updated 4 months ago
Version 1.0.0
Models

Add to Favorites

Why it matters

Develop a clear, concise, and honest positioning statement for your product or service. This asset guides founders and teams through a structured exercise combining competitive research and strategic questioning.

Outcomes

What it gets done

01

Conduct parallel competitive analysis (direct and adjacent).

02

Facilitate a forced-choice strategic questioning exercise.

03

Synthesize team responses into an alignment map.

04

Produce a positioning statement under 30 words.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/positioning-plugin | bash

Overview

Positioning Plugin for Claude Code

A structured Claude Code positioning exercise that runs competitive research, forces the team through hard forced-choice questions independently, and synthesizes an honest sub-30-word positioning statement with verifiable claims. Use when a team's product messaging has gone vague or team members would describe the product differently, and positioning needs to be grounded in real competitive research.

What it does

This skill runs a structured positioning exercise for Claude Code that produces an honest, sub-30-word positioning statement by forcing hard choices rather than accepting vague, all-things-to-everyone descriptions. Invoked via /positioning:positioning, its six-step process: gather context (what the product does, who it serves, what stage the company is at), run parallel competitive research covering both direct and adjacent competitors, generate four forced-choice questions informed by the real competitor names surfaced in that research, distribute a copy-paste questionnaire so team members answer independently rather than converging prematurely in discussion, synthesize the team's answers into an alignment map surfacing contradictions and surprises across responses, and produce the final output - a positioning statement under 30 words, with every supporting section kept under 200 words.

Its core discipline is that every question is a forced choice - there is no "all of the above" option, because the exercise's value comes specifically from the discomfort of having to choose one thing over another rather than hedging. Quality rules apply to the final output: no sentence over 20 words, no unverifiable marketing adjectives like "innovative," "cutting-edge," or "world-class," and every claim must either be true today or be explicitly marked as an aspirational bet rather than presented as already accomplished. An example output illustrates the target format: "We help DevOps teams resolve incidents before customers notice, through causal root-cause analysis, unlike dashboard-first monitoring tools" - naming a specific audience, a specific mechanism, and an explicit contrast against a named category of alternative.

When to use - and when NOT to

Use this skill when a team needs to align on product positioning - especially when messaging has drifted vague, when different team members would describe the product differently, or when competitive research needs to directly inform the hard choices positioning requires, rather than positioning being written in isolation from what competitors actually claim.

It is not a tool for generating marketing copy or a tagline in isolation - the forced-choice, competitor-informed, team-alignment process is the point, and skipping straight to a polished statement without the research and team exercise steps defeats the purpose of the exercise.

Inputs and outputs

Input is context about the product/company (what it does, who it serves, current stage) plus independent team responses to a forced-choice questionnaire informed by competitive research. Output is a synthesis showing team alignment, contradictions, and surprises, culminating in a final positioning statement under 30 words with all supporting sections under 200 words each, following the quality rules for verifiable, concise claims.

/plugin marketplace add Gerstep/positioning-plugin
/plugin install positioning@positioning-plugins

Integrations

Installed as a Claude Code plugin via the plugin marketplace, run with the /positioning:positioning command; licensed under MIT.

Who it's for

Founders, product marketers, or leadership teams who need to align on and produce an honest, defensible positioning statement grounded in real competitive research rather than internal assumption or unverified marketing language.

Source README

Positioning Plugin for Claude Code

Structured positioning exercise that produces an honest, sub-30-word positioning statement. Research competitors, force hard choices, align the team.

Install

/plugin marketplace add Gerstep/positioning-plugin
/plugin install positioning@positioning-plugins

Then run: /positioning:positioning

How it works

  1. Context - What you do, who you serve, what stage
  2. Research - Parallel competitive analysis (direct + adjacent competitors)
  3. 4 forced-choice questions - Informed by real competitor names from research
  4. Team exercise - Copy-paste questionnaire for independent team responses
  5. Synthesis - Alignment map, contradictions, surprises across team answers
  6. Output - Positioning statement under 30 words, all sections under 200 words

Every question is a forced choice. No "all of the above." The pain of choosing is the exercise.

Example output

We help DevOps teams resolve incidents before customers notice,
through causal root-cause analysis, unlike dashboard-first monitoring tools.

Quality rules

  • No sentence over 20 words
  • No unverifiable adjectives ("innovative", "cutting-edge", "world-class")
  • Claims are either true today or explicitly marked as bets
  • Positioning statement under 30 words

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.