define-positioning
Skill1 starsChanged 3 months agoMITView on GitHub
Define what the business is the obvious choice for and for whom — positioning statement, worldview, status shift, messaging hierarchy, brand voice. Run after offer design; rerun only when strategy changes.
In this repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-funnelSkill
- close-dealSkill
- connect-toolsSkill
- create-contentSkill
- design-offerSkill
- experimentSkill
- grow-referralsSkill
- grow-seoSkill
- health-checkSkill
- launch-campaignSkill
- launch-productSkill
- manage-pipelineSkill
- measureSkill
- plan-strategySkill
- research-marketSkill
- review-monthlySkill
- run-adsSkill
- run-outboundSkill
- run-partnershipsSkill
- setup-teamSkill
- tune-revopsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
No credible open corner exists on the chosen axes → pick different axes or recommend narrowing the segment.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/define-positioning — Claim a Corner of the Customer's Mind
Inputs: knowledge/audience-profiles.md, knowledge/research/competitors.md, knowledge/offer.md.
Agents: brand-strategist leads; copywriter phrases.
Method: knowledge/methods/positioning-and-audience.md.
Steps
- Choose the axes. From research, the two attributes this audience cares about most when choosing. Plot competitors; find the credible open corner — edges beat middles.
- Write the positioning statement. "For [narrow who], [name] is the [category] that [distinct what]" — specific enough that the wrong customers self-select out.
- Articulate the worldview. The belief our best customers already hold that makes us their natural choice. State it as they'd say it.
- Name the status shift. What buying this changes about the buyer's standing — with peers, colleagues, family, or self-image. From → to, explicitly.
- Build the messaging hierarchy. One core promise; three supporting pillars; verifiable proof under each. This plus the approved-claims list is what every future artifact draws from.
- Define the voice. 3–4 attributes with this-not-that examples, written into the Brand voice section of
standards/voice.md— the single canonical voice source (brand-strategist is its sole author).knowledge/positioning.mdlinks there; it never restates voice. - Stress-test. Would the beachhead customer recognize themselves? Could a competitor claim the same sentence truthfully (if yes, sharpen)? Does the offer, price, and positioning tell one consistent story?
- Operator sign-off, then it's law: all copy, pages, and campaigns must align until strategy formally changes.
Before you start
- Required inputs:
knowledge/offer.mdandknowledge/audience-profiles.mdatseeded+,knowledge/research/competitors.mdpresent — if missing, run/design-offer//research-marketfirst. - Scan
knowledge/decision-log.mdfor tagspositioning,voice— positioning changes invalidate downstream copy; supersede deliberately, never drift. - Gate check: operator sign-off in step 8 is required before any artifact uses the new positioning.
If things go wrong
- Offer and audience research contradict each other (the offer serves a segment research rejected) → stop and resolve with the operator before positioning either.
- No credible open corner exists on the chosen axes → pick different axes or recommend narrowing the segment; never claim a corner a competitor already owns.
- Operator unavailable for sign-off → park in
knowledge/pending.md; existing positioning (if any) remains law until then.
Outputs
knowledge/positioning.md: statement, worldview, status shift, messaging hierarchy, approved claims + proof, naming/tagline decisions. Brand voice recorded in standards/voice.md. Close with the report per templates/skill-report.md.
Writeback
knowledge/positioning.md; standards/voice.md (Brand voice section); decision (tags: positioning, voice) to knowledge/decision-log.md.
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.

