position-and-launch-hypothesis
Skill4 starsChanged 20 days agoMITView on GitHub
Turn product evidence into a testable positioning and launch hypothesis for a defined buyer or user. Use when deciding who should adopt a product, why they should choose it, and which launch signal would provide evidence. Do not use to fabricate demand or publish a launch without authorization.
In this repository9 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 15
Write the positioning hypothesis: For [audience in situation], [product] helps [progress] unlike [alternative] because [credible …
- Distinctive: line 38
Do not treat clicks, novelty, compliments, or GitHub stars as proof of retained value.
- Distinctive: line 39
Do not invent testimonials, customer counts, outcomes, or competitive superiority.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Position and Launch Hypothesis
Connect the product promise to a specific audience, current alternative, credible differentiation, channel, and interpretable signal.
Form the hypothesis
- Separate user from buyer when they differ. State the situation, struggle, desired progress, and current alternative.
- Trace every claimed value or differentiator to product evidence. Mark unsupported claims as hypotheses.
- Choose one primary segment and one adoption moment for this test.
- Write the positioning hypothesis:
For [audience in situation], [product] helps [progress] unlike [alternative] because [credible difference]. - Choose the smallest market-facing artifact or channel that can test the important claim: conversation, message test, landing page, onboarding, pricing probe, or limited launch.
- Define the behavior that would count as a meaningful signal. Separate attention from adoption and value.
- Set support / reject / reframe criteria, duration or sample boundary, and the decision owner.
Output
## Audience and adoption situation
## Evidence and unsupported claims
## Positioning hypothesis
## Launch experiment
## Signal hierarchy
- Attention:
- Intent:
- Activation:
- Value / retention:
## Support / reject / reframe criteria
## Decision after the testBoundaries
- Do not treat clicks, novelty, compliments, or GitHub stars as proof of retained value.
- Do not invent testimonials, customer counts, outcomes, or competitive superiority.
- Creating a plan or draft does not authorize publishing, outreach, advertising, or account changes.
- Preserve the shared product context rather than creating a conflicting marketing truth.
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.

