product-positioning-expert

product-positioning-expert is a command for Claude Code from maigentic/stratarts. It costs 29 tokens per session (9,058 once invoked), scanned A, original, MIT.

A product-positioning command based on April Dunford’s framework. Product positioning explains who a product is for, what makes it different, and why that difference matters to customers.

In plain words
What is it for?
Use it to create positioning statements, value propositions, messaging levels, competitive comparisons, messaging themes, and channel-specific messaging guides.
Why use it?
It helps turn unclear or inconsistent product messaging into a structured story about customers, alternatives, distinctive qualities, value, and market context. This makes it easier to communicate the product across different channels.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: positional $N argument.

Part of the stratarts plugin — 27 commands shipped together

Good fit Use it to create positioning statements, value propositions, messaging levels, competitive comparisons, messaging themes, and channel-specific messaging guides.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/maigentic/stratarts/product-positioning-expert
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/maigentic/stratarts

Made for: Claude Code.

Or install stratarts, the plugin that ships this one along with the rest of its 27 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for product-positioning-expert

README.md
[![agentmods](https://agentmods.dev/badge/commands/maigentic/stratarts/product-positioning-expert.svg)](https://agentmods.dev/commands/maigentic/stratarts/product-positioning-expert)
Your own site
<a href="https://agentmods.dev/commands/maigentic/stratarts/product-positioning-expert"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/product-positioning-expert.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 9,058 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.09058
Opus 5 $0.00015 $0.04529
Sonnet 5 $0.00006 $0.01812
Haiku 4.5 $0.00003 $0.00906

Measured 8d ago against content hash 5306ad0dc01e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

product-positioning-expert scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

stratarts/commands/product-positioning-expert.md · 1,310 lines

How it starts

The opening of the file, as written. The whole thing — 1,310 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Product Positioning Expert

You are an expert positioning strategist specializing in crafting clear, differentiated positioning and messaging that resonates with target customers and stands out from competitors. Your role is to help founders articulate "who it's for, what it does, and why it matters" in a way that drives conversion and builds brand.

Purpose

Guide the user through a comprehensive positioning strategy development process using proven frameworks (April Dunford's Positioning Canvas, Messaging Hierarchy, Jobs-to-be-Done Messaging). Produce a detailed positioning & messaging strategy (2,500-3,500 words) including positioning statement, value propositions, messaging pillars, and channel-specific messaging.

Framework Applied

April Dunford's Positioning Framework + Messaging Hierarchy:

  • Competitive Alternatives (What would customers use if you didn't exist?)
  • Unique Attributes (What do you have that alternatives lack?)
  • Value (What value do those attributes enable?)
  • Target Customers (Who cares a lot about that value?)
  • Market Category (What context makes your value obvious?)

Workflow

Step 0: Project Directory Setup

CRITICAL: Establish project directory BEFORE proceeding to context detection.

Present this to the user:

════════════════════════════════════════════════════════════════════════════════
STRATARTS: PRODUCT POSITIONING EXPERT
════════════════════════════════════════════════════════════════════════════════

April Dunford's positioning framework for clear market differentiation.

⏱️  Estimated Time: 75-120 minutes
📊 Framework: Positioning Canvas + Messaging Hierarchy
📁 Category: foundation-strategy

════════════════════════════════════════════════════════════════════════════════

Then immediately establish project directory:

════════════════════════════════════════════════════════════════════════════════
PROJECT DIRECTORY SETUP
════════════════════════════════════════════════════════════════════════════════

StratArts saves analysis outputs to a dedicated '.strategy/' folder in your project.

Current working directory: {CURRENT_WORKING_DIR}

Where is your project directory for this business?

a: Current directory ({CURRENT_WORKING_DIR}) - Use this directory
b: Different directory - I'll provide the path
c: No project yet - Create new project directory

Select option (a, b, or c): _

Read the full file on GitHub · 1,310 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 1,310 lines · 29 tokens per session scan A 5306ad0dc01e

Subscribe to this mod's changes

product-positioning-expert is a command published in the GitHub repository maigentic/stratarts (40 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 9,058 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.