positioning-workshop
Skill9 starsChanged 6 months agoMITView on GitHub
Full structured positioning exercise with competitive research, forced-choice questions, team alignment, and synthesis. Produces a sub-30-word positioning statement. For quick help with taglines, value props, or messaging tweaks, use positioning-messaging instead.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- deanpeters/Product-Manager-Skillstheir own version, first seen Oct 25, 2026
- NinjaSln-labs/agent-skillstheir own version, first seen Oct 2, 2026
- agrivisionai/claude-skillstheir own version, first seen Jul 14, 2026
- styfinity/claude-marketing-departmenttheir own version, first seen Jul 8, 2026
- DIAL-Studio/pm-agent-harness-kittheir own version, first seen Jul 8, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- deanpeters/Product-Manager-Skills★ 7.7ksame name
- DIAL-Studio/pm-agent-harness-kit★ 12same name
- styfinity/claude-marketing-department★ 6same name
- paulnugentuk/pmmstack★ 2same name
- agrivisionai/claude-skills★ 1same name
- nandanosql/all_in_one_pm_skills★ 1same name
- NinjaSln-labs/agent-skills★ 1same name
- vijaysuperpositionist/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository78 other files it gives its agents.
- anti-pattern-auditSkill
- brand-storytellingSkill
- business-investigationSkill
- ceo-weekly-reviewSkill
- cold-emailSkill
- community-buildingSkill
- company-intelSkill
- competitive-analysisSkill
- competitor-researchSkill
- composio-cliSkill
- conducting-user-interviewsSkill
- content-strategySkill
- copywritingSkill
- daily-recapSkill
- decision-playbookSkill
- designing-growth-loopsSkill
- discovery-debriefSkill
- email-sequenceSkill
- enterprise-salesSkill
- evening-recapSkill
- exa-code-searchSkill
- exa-company-researchSkill
- exa-lead-genSkill
- exa-people-researchSkill
- exa-personal-siteSkill
- exa-x-searchSkill
- feedback-trackerSkill
- find-email-by-nameSkill
- focus-keeperSkill
- founder-salesSkill
- fpf-problem-solvingSkill
- github-stars-monitorSkill
- google-calendarSkill
- grafana-monitoringSkill
- humanizerSkill
- hypothesis-trackerSkill
- idea-generatorSkill
- install-openclaw-to-digitaloceanSkill
- install-openclaw-to-hetznerSkill
- install-openclaw-to-ycSkill
- launch-marketingSkill
- lead-enrichmentSkill
- measuring-product-market-fitSkill
- meeting-prepSkill
- metrics-briefingSkill
- morning-briefSkill
- openclaw-guideSkill
- openclaw-user-onboardingSkill
- orthogonalSkill
- outreach-senderSkill
- person-lookupSkill
- ph-launch-timelineSkill
- pipeline-managerSkill
- positioning-messagingSkill
- posthog-analyticsSkill
- prepare-yc-workshopSkill
- pricing-strategySkill
- problem-definitionSkill
- product-hunt-launchSkill
- product-led-salesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
- Distinctive: line 10
Follow output preferences from USER.md (language, format, platform constraints).
- Distinctive: line 41
If the user provides a file path or URL: read it.
- Distinctive: line 126
After the four questions, immediately ask: "Now write your positioning statement.
- Distinctive: line 162
Ask: "Send this to your team and paste all their replies here when you have them.
- Distinctive: line 166
When user pastes team replies, analyze them:
- Distinctive: line 205
No sentence over 20 words
- Distinctive: line 206
No unverifiable adjectives (remove "innovative", "cutting-edge", "world-class", "unique")
- Distinctive: line 207
Every claim must be either (a) already true or (b) explicitly marked as a bet
- Distinctive: line 208
If aspirational, say "By [date], we plan to..." — not "We are..."
- Distinctive: line 215
If user wants to iterate, identify which section needs work.
- Distinctive: line 221
Don't use marketing language: If it sounds like a SaaS landing page, rewrite it.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
[YOUR_PRODUCT] Context
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
Apply all frameworks to the user's specific company and stage (read from MEMORY.md).
Follow output preferences from USER.md (language, format, platform constraints).
For chat platforms: max 15 lines, no markdown tables, be concrete and actionable.
Positioning Workshop
Structured positioning statement exercise. Combines deep competitive research with forced-choice strategic questions to produce an honest, compressed positioning statement.
Designed for teams that can't answer "why us?" in one sentence.
Philosophy
Most positioning exercises produce corporate fluff because they skip the hard questions. This skill forces honesty by:
- Researching competitors BEFORE asking questions (so you can't hide from reality)
- Making every question a forced choice (no "all of the above")
- Requiring the team to write independently, then collide answers
- Compressing the final output to under 30 words
The output is not marketing copy. It's a strategic alignment tool.
Workflow
PHASE 1: Context gathering
Collect basic info:
- "What does the company do? (2-3 sentences, plain language)"
- "Who is the target customer today?"
- "What stage? What's the team size?" — Options: [Pre-seed solo/duo, Pre-seed with team (3-8), Seed, Series A+]
- "Is there an existing website, pitch deck, or memo I should read?"
If the user provides a file path or URL: read it. Extract product description, claimed differentiators, current messaging, pricing, and team.
PHASE 2: Competitive research
Launch 2 parallel research agents:
Agent 1: Direct competitors
Research the competitive landscape for: [company description from Phase 1].
Use web search and competitor websites.
Find:
1. The 3-5 closest competitors (same customer, same problem)
2. For each: one-liner positioning, pricing, key differentiator, weakness
3. What do ALL of them say? (common claims = table stakes, not differentiators)
4. What does NONE of them say? (potential white space)
Output as a markdown table + 3 bullet summary.Agent 2: Adjacent/aspirational competitors
Research companies adjacent to: [company description from Phase 1].
Use web search.
Find:
1. 2-3 companies solving a related problem for the same customer
2. 2-3 companies solving the same problem for a different customer
3. Any company that this team might secretly aspire to be (the "we're like X but for Y" reference)
For each: one-liner, why they matter as context.Launch both agents in parallel. After agents return, present findings and ask:
- "Anything missing or wrong in this competitive picture?" — Options: [Looks right, Let me add/correct]
- "Which competitor do founders most often compare you to?"
PHASE 3: The four questions
Present four positioning questions. Each question is informed by the competitive research.
Frame questions using SPECIFIC competitor names and findings from Phase 2. Do not use generic placeholders.
Q1: The customer test
Your ideal customer is evaluating you against [TOP COMPETITOR 1] and [TOP COMPETITOR 2].
They can only pick one. Why do they pick you?
Rules:
- Don't say "price" or "we're cheaper"
- Don't say "better technology" without specifics
- Don't say "customer service" (everyone says this)
Options: [Generate 3-4 options based on research, each a distinct strategic direction] + "Something else"Q2: The honest gap
What is the single biggest reason your ideal customer says NO today?
Be specific. Not "we're early stage" — that's a cop-out.
Options: [Generate 3-4 options based on competitive weaknesses found in research] + "Something else"Q3: The core bet
You can only invest in ONE of these directions for the next 6 months. Which one?
Options: [Generate 3-4 options based on white space found in research,
each with a 1-sentence description of what it means concretely] + "Something else"Q4: Market scope
Which market are you actually in? Pick the one that defines your roadmap.
Options: [Generate 3-4 market definitions from narrow to broad,
based on the company's product and competitive research]Q5: Your first draft
After the four questions, immediately ask: "Now write your positioning statement. Under 30 words. Don't overthink it — gut reaction based on what you just answered." Template: We help [WHO] achieve [WHAT] through [HOW], unlike [ALTERNATIVE].
Save the user's draft verbatim. In Phase 6, show it side-by-side with the final synthesized version.
PHASE 4: Team collection
Generate a clean markdown block that the user can copy-paste to their team:
# Positioning Exercise — [Company Name]
Answer each question independently. Don't discuss with teammates first.
Spend max 10 minutes total. Gut reactions > polished answers.
## 1. The customer test
[Customized question with competitor names from research]
## 2. The honest gap
[Customized question]
## 3. The core bet
[Customized question with forced-choice options]
## 4. Market scope
[Customized question with scope options]
## 5. Positioning statement
Fill in, keep under 30 words:
We help [WHO] achieve [WHAT] through [HOW], unlike [ALTERNATIVE].
---
Return all answers to [user name] by [user specifies deadline].Ask: "Send this to your team and paste all their replies here when you have them. How many people will respond?"
PHASE 5: Synthesis
When user pastes team replies, analyze them:
- Alignment map — Where does everyone agree? (These are real. Use them.)
- Contradiction map — Where do people disagree? (These are the strategic decisions that need to be made.)
- Surprise findings — Anything one person said that nobody else did but is clearly right.
- Gap analysis — Questions nobody answered well (signals the team hasn't thought this through).
Present analysis, then ask for each contradiction: which direction do you want to go? (forced binary choice)
PHASE 6: Final positioning statement
Output format:
# [Company Name] — Positioning Statement
## The customer test
[2-3 sentences. Lead with the answer. No fluff.]
## The honest gap
[1-2 sentences. Brutally honest.]
## The core bet
[2-3 sentences. What you're building, what exists today vs. planned.]
## Market scope
[1 sentence. The market you chose and what it excludes.]
## Positioning statement
[Under 30 words]
We help [WHO] achieve [WHAT] through [HOW], unlike [ALTERNATIVE].
## Your first draft vs. final
> **Your draft:** [user's verbatim draft from Phase 3 Q5]
> **Final:** [synthesized version above]
> **What changed:** [1-2 sentences on what shifted and why]Quality rules:
- No sentence over 20 words
- No unverifiable adjectives (remove "innovative", "cutting-edge", "world-class", "unique")
- Every claim must be either (a) already true or (b) explicitly marked as a bet
- If aspirational, say "By [date], we plan to..." — not "We are..."
- Total length: under 200 words for all sections combined
Save to: ask the user where they'd like to save the output.
PHASE 7: Iteration (optional)
If user wants to iterate, identify which section needs work. Re-run only that section's question with tighter constraints.
Anti-patterns to avoid
- Don't generate positioning without research. The competitive context makes questions sharp.
- Don't let the user skip the team exercise. Solo positioning statements are echo chambers.
- Don't use marketing language. If it sounds like a SaaS landing page, rewrite it.
- Don't accept "all of the above" answers. Force choices. The pain of choosing IS the exercise.
- Don't make the final statement longer than 30 words. Compression is clarity.
Related Skills
- positioning-messaging — quick help with taglines, value props, messaging tweaks
- competitive-analysis — strategic competitive frameworks
- brand-storytelling — company narrative and pitch story
- problem-definition — clarify what problem you're solving before positioning
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

