Positioning plugin
A 15-minute forced-choice session with your agent that produces a startup positioning statement and a proof plan
- 109 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- Markdown instructions, writes files only into the positioning/ folder
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/positioningDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Markdown instructions, writes files only into the positioning/ folder
This is third-party code. Review the repository files before installing.
What it does
On /positioning the agent asks about ten questions one at a time, each requiring a single choice. Meanwhile it researches competitors and shows what they all say and what none of them say. The result is a positioning statement under 30 words, message architecture, a category decision, a brand archetype and three dated proofs for the next 90 days. With several co-founders the skill compiles their answers, surfaces contradictions and forces decisions.
Who it is for. Startup founders and product teams who need to articulate positioning quickly and agree on it.
Good fit when
- You need to articulate how the product differs from competitors
- Co-founders describe the company differently
- You are preparing a landing page, pitch or market messaging
Not a fit when
- You need full market research backed by data
- Your positioning is already settled and validated by the market
Example request
/positioningLimitations
Competitor research depends on the agent's web access and is skipped without it. Claims that cannot be verified are rewritten as dated commitments. Materials and examples are in English.
How to disable. Remove the plugin via /plugin in Claude Code or in Codex plugin settings.
FAQ
Where is the output saved?
In the positioning/ folder of the current project: each founder's answers file and the final document.
What about solo founders?
The final pack is produced right after the first session, no second step needed.
Discussion
No questions or reviews yet.
Related
PluginsClaude Code skills for founders: pricing and launch plans, PRDs, landing page reviews, social posts and cold outreach
Twenty go-to-market skills for technical founders: positioning, first users, launch and pricing
A large marketing plugin: strategy, SEO and GEO, paid media, content, CRM and analytics grounded in a brand profile
A set of skills for solopreneurs: SEO and GEO, demand research, domains, logo and banner generation, social scraping
A bilingual pack of marketing skills for agents: strategy, content, performance, design and role operations
A skill that reads your project code and builds a short launch video with one command
README in short
The plugin walks a founder through a short choice session: category, target customer and who to ignore, value, positioning statement, a memorable phrase, archetype and 90-day proofs. At the end the agent fact-checks the statement like a skeptical customer. Each co-founder runs the session separately, then answers are compiled. Installation is documented for Claude Code, Cowork and Codex, and the skill follows the Agent Skills spec. MIT license.
README badge
Original SKILL.md
--- name: positioning description: Run a 15-minute forced-choice positioning session for a startup. Pick a category path (compete, reframe, or create), decide who you serve and who you ignore, write a positioning statement under 30 words, find the mind-virus phrase, choose a brand archetype, and plan a 90-day window of proof. Each co-founder runs it solo; the skill then compiles all answers, surfaces contradictions, and forces decisions. Use when a company needs positioning, messaging, category strategy, a value proposition, or founder alignment on "why us". license: MIT metadata: author: "Stepan Gershuni, cyber.fund" version: "2.0.0" --- # Positioning A 15-minute forced-choice session that produces a positioning statement and the artifacts a startup needs to hold a position: message architecture, mind virus, compass, ignore list, worldview, archetype, and a 90-day proof plan. Position or be positioned. If you don't pick a category, you will be assigned one. The market's default setting is disbelief, so competition has shifted from making claims to surviving verification. This skill forces the choices, then makes every claim either provable today or a dated bet. ## Operating rules (read first) **Questions.** If an interactive question tool is available (for example AskUserQuestion in Claude Code or Cowork), use it for every forced choice. Otherwise ask in plain text: one question at a time, numbered options, wait for the answer. Never stack questions in plain-text mode. **Forced choice.** No "all of the above". Gut answers over polished answers — tell the user 30 seconds per question is enough. The pain of choosing is the exercise. **Time.** The session targets 15 minutes total. Never block on research; never loop. Phase budgets are in the session script. If research has not returned by the statement phase, proceed without it and mark the pack "research pending". **Research.** If a subagent tool is available, launch research in the background during setup. If only web search is available, run a few quick searches inline between phases. If there is no web access, skip research and say so in the output. Never invent competitors. **Files.** All artifacts live in `positioning/` under the current working directory (create it if needed). Never overwrite another founder's answers file.