positioning-workshop

Overview of positioning-workshop skill

positioning-workshop is an interactive skill for turning vague product messaging into a clear positioning decision: who the product is for, what problem it solves, what category it belongs in, and why it is meaningfully different. It is best for product managers, founders, and Product Marketing teams that need a sharper story before a launch, PRD, website update, or sales enablement reset.

What positioning-workshop is for

The positioning-workshop skill helps you run a structured session instead of a loose brainstorm. The goal is not to generate slogans; it is to force deliberate choices about target customer, unmet need, category, benefits, and differentiation. That makes it especially useful when everyone agrees the messaging is “fine” but no one can explain it crisply.

Why this skill is different

Unlike a generic prompt, positioning-workshop adapts its questions based on your answers, so the conversation can narrow from broad market language to specific positioning decisions. That interaction matters when the real blocker is not writing quality but strategic ambiguity. It is a strong fit for positioning-workshop for Product Marketing teams that need alignment across product, marketing, and leadership.

When to use it

Use positioning-workshop when:

• your homepage copy sounds generic
• a product has too many possible audiences
• you need a category and differentiation story, not just features
• stakeholders disagree on who the primary buyer is
• you want stronger launch inputs before producing final copy

How to Use positioning-workshop skill

Install positioning-workshop

Install with the repo skill command shown in the source: npx skills add deanpeters/Product-Manager-Skills --skill positioning-workshop. After installation, confirm the skill is available in your skills directory and that the positioning-workshop skill is selected in your agent or editor workflow.

Start with the right inputs

The skill works best when you supply a rough but concrete starting point. A strong prompt should include:

• product name and one-line description
• target market or customer type
• what users are currently doing instead
• the main pain point or unmet need
• known competitors or alternatives
• any constraints on category, tone, or launch context

For example, instead of “help me position our product,” use: “Run a positioning-workshop for our B2B analytics tool for finance teams. We replace spreadsheet-based reporting, compete with Looker and Tableau, and need a clearer message for a mid-market launch.”

Read these files first

Start with SKILL.md, then inspect README.md, AGENTS.md, metadata.json, and any rules/, resources/, references/, or scripts/ folders if they exist in your environment. For this repository, SKILL.md is the main source of truth, so treat it as the core implementation guide for positioning-workshop usage.

Run the workshop effectively

Treat the skill like a guided interview. Give short, specific answers and let it narrow the decision tree. If you do not know the answer to a question, say so explicitly instead of guessing. The output improves when you distinguish between:

• the user you want to win
• the problem they feel most sharply
• the category language you can credibly own
• the benefits you can prove
• the alternatives you want to displace

positioning-workshop skill FAQ

Is positioning-workshop only for Product Marketing?

No. It is strongest for Product Marketing, but product managers and founders can use it to prepare a better positioning foundation before handoff. The positioning-workshop skill is especially useful when you need strategic clarity before copywriting starts.

What should I have ready before using it?

Have a draft customer segment, a short product summary, and at least one alternative the product replaces or outperforms. If you can also name the launch goal or audience, the positioning-workshop guide can get to useful output faster.

Is this better than a normal prompt?

Usually yes, if your problem is structure and decision quality. A normal prompt can produce messaging, but positioning-workshop is designed to surface the choices behind the messaging, which reduces generic output and helps teams agree on the story.

When should I not use it?

Do not use positioning-workshop if you only need a quick headline rewrite, a one-page value prop polish, or a tactical copy edit. It is for strategic positioning work, not lightweight wording cleanup.

How to Improve positioning-workshop skill

Give it fewer, sharper options

The biggest improvement comes from reducing ambiguity. If you provide five possible audiences, four competing benefits, and no category preference, the workshop will spend time sorting inputs instead of sharpening the position. For better positioning-workshop usage, bring one likely primary segment and one backup only if needed.

Include real tradeoffs

Good positioning requires exclusion as well as inclusion. Tell the skill what you are not, what you refuse to optimize for, and which competitor frame you want to avoid. That helps the workshop produce positioning that is defensible rather than broadly appealing.

Iterate on the first output

Use the first result as a draft decision, not a final artifact. Then refine it with evidence: sales objections, customer interview notes, conversion data, or competitor pages. The best positioning-workshop guide behavior is iterative—tighten the target, then retest the category and benefit claims.

Watch for common failure modes

The most common failure is accepting language that sounds strategic but could apply to any product. Another is asking the skill to invent proof it does not have. Improve results by supplying concrete market evidence, naming real alternatives, and asking the skill to sharpen one specific positioning axis at a time.