Skip to content

AI agent skills for startup validation, competitive intelligence, and planning

feat: add messaging-implications deliverable to startup-positioning

Ferdinando Bonsegna51b282906f19
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json
index 6560f43..c5b72c5 100644
--- a/.claude-plugin/marketplace.json
+++ b/.claude-plugin/marketplace.json
@@ -6,7 +6,7 @@
},
"metadata": {
"description": "AI agent skills for startup design, validation, competitive intelligence, and planning",
- "version": "1.3.0"
+ "version": "1.4.0"
},
"plugins": [
{
diff --git a/README.md b/README.md
index 4db772a..a6c0758 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,8 @@
-# Startup Skills for AI Agents
+# Startup Skill
-Everything you need to validate and launch a startup — researched by AI agents, not guesswork.
+Open-source AI startup strategy toolkit. From startup idea to validated strategy in one afternoon. Radically honest. Free.
-These skills turn Claude into a startup analyst. They search the web, profile competitors, mine customer reviews, reverse-engineer pricing, and produce structured deliverables you can actually use: battle cards, financial projections, positioning docs, risk scorecards.
+What a $10K strategy consultant would deliver: market research, competitive battle cards, positioning, financial projections, and a 30-day action plan. If your idea should die, it will tell you.
Works with [Claude Code](https://claude.ai/claude-code) and any agent that supports skills.
@@ -14,11 +14,9 @@ Works with [Claude Code](https://claude.ai/claude-code) and any agent that suppo
| Skill | What you get |
|-------|-------------|
-| [startup-design](startup-design/) | A complete startup plan: market research, strategy, brand, product definition, financial projections, and validation experiments. 8 phases, 11 research agents, one command. |
-| [startup-competitors](startup-competitors/) | Battle cards for every competitor, a pricing landscape with reverse-engineered tiers, a feature matrix, and a strategic report — built from real reviews, forums, and web data. |
-| [startup-positioning](startup-positioning/) | Market positioning strategy using April Dunford's framework, enriched with JTBD, Moore, and Neumeier. Produces a positioning doc, positioning statements, competitive alternatives map, and market category analysis. 3 phases, 4 research agents. |
-
-Coming soon: `startup-pitch` (investor deck generation).
+| [startup-design](startup-design/) | Complete startup strategy: market research, competitive analysis, brand, product definition, financial projections, and validation experiments. 8 phases, 30+ structured deliverables. |
+| [startup-competitors](startup-competitors/) | Battle cards for every competitor, pricing landscape, feature matrix, and strategic report. Built from real reviews, forums, and web data. |
+| [startup-positioning](startup-positioning/) | Market positioning using April Dunford's framework. Positioning doc, competitive alternatives map, market category analysis, and messaging implications. |
## Usage
diff --git a/startup-positioning/SKILL.md b/startup-positioning/SKILL.md
index a76828e..a3a39cc 100644
--- a/startup-positioning/SKILL.md
+++ b/startup-positioning/SKILL.md
@@ -176,10 +176,13 @@ Every deliverable file must start with a standardized header: `# {Title}: {produ
- Strategic recommendations and next steps
- Data gaps & limitations
-**`{project-name}/positioning-statement.md`** — Three formats:
+**`{project-name}/positioning-statement.md`** — Statements and messaging:
- Moore template: "For [target] who [need], [product] is a [category] that [benefit]. Unlike [alternative], we [differentiator]."
- Neumeier Onliness Statement (basic + extended)
- Elevator pitch (30-second version)
+- Tagline candidates with stress-tested "Possible Misread" column
+- One-liner variants for different channels (GitHub, marketplace, social, elevator)
+- Freemium positioning (if applicable)
**`{project-name}/competitive-alternatives.md`** — Complete alternatives map:
- All alternatives (direct, adjacent, manual, status quo)
@@ -193,6 +196,15 @@ Every deliverable file must start with a standardized header: `# {Title}: {produ
- Implementation (category label, tagline direction, buyer expectation alignment)
- Red flags and yellow flags
+**`{project-name}/messaging-implications.md`** — Bridge from positioning to copy:
+- Messaging hierarchy (what to communicate first, second, third)
+- Category label (exact phrase to use everywhere)
+- Value anchor (what to compare value to, separate from category)
+- Customer language vs. category language map (which words are customer verbs, which are category nouns)
+- Words to use / avoid
+- Social proof guidelines
+- Freemium positioning (if applicable)
+
### Raw Data
Each agent saves its raw output to `{project-name}/raw/`. The synthesis phase reads these raw files and produces the polished deliverables above. Agents must NOT write directly to deliverable paths — raw and synthesized output are separate.
@@ -238,5 +250,5 @@ Read only what you need for the current phase.
| `research-principles.md` | Before starting Phase 2 | ~65 | Source quality, cross-referencing, data gaps |
| `research-wave-1-alternatives.md` | When running Wave 1 | ~235 | Agent templates for alternatives + customer intel |
| `research-wave-2-market-frame.md` | When running Wave 2 | ~210 | Agent templates for categories + trends |
-| `research-synthesis.md` | After both waves complete | ~290 | Synthesis protocol, Dunford process, validation tests |
+| `research-synthesis.md` | After both waves complete | ~380 | Synthesis protocol, Dunford process, validation tests, messaging implications |
| `frameworks.md` | During Phase 3 | ~133 | Dunford/Moore/Neumeier/JTBD/Ries reference |
diff --git a/startup-positioning/references/research-synthesis.md b/startup-positioning/references/research-synthesis.md
index 89413c8..e3d916a 100644
--- a/startup-positioning/references/research-synthesis.md
+++ b/startup-positioning/references/research-synthesis.md
@@ -57,6 +57,12 @@ Work through each component in order. Each one builds on the last.
- Test: Would a customer care about this? Would they pay for it?
- If a value theme doesn't connect to a real customer pain from Wave 2, drop it
+**Category language vs. Customer language check:**
+Customers often describe their problem using words that would position the product in the wrong category. Example: founders search "validate my startup idea" (customer language), but "validation tool" triggers the wrong buyer expectations (instant score, shallow analysis). When this tension exists:
+- Document both the customer verbs and the category nouns
+- Recommend bridging in copy: use customer verbs + category nouns (e.g., "validate your startup idea" as the action, "validated strategy" as the outcome)
+- Flag this explicitly in the messaging-implications deliverable so copywriters know which words are customer-language (use as verbs) and which are category-language (use as outcomes/nouns)
+
### 4. Best-Fit Customers
- Pull from `raw/customer-intelligence.md` — best-fit customer profile
@@ -74,6 +80,7 @@ Work through each component in order. Each one builds on the last.
- The right category makes the value OBVIOUS without explanation
- If unsure between two: default to the one where the product has the strongest existing proof points
- Consider: existing category, subcategory, or new category (new is highest risk)
+- **Separate three things clearly:** (1) the category label (what the product IS), (2) the value anchor (what you compare value TO), (3) the distribution descriptor (HOW to get it). These are different and serve different purposes in copy. Example: category = "AI Startup Strategy Toolkit", value anchor = "what a $10K consultant delivers", distribution = "open-source Claude skill"
### 6. Trend Overlay (Optional)
@@ -194,6 +201,11 @@ If any test fails, iterate on the 5+1 components. Do not ship weak positioning.
| Market Category | ... | ... |
| Overall | ... | ... |
+## Strategic Recommendations
+{next steps for implementing the positioning}
+
+**Social proof warning:** Do not fabricate or pre-write social proof quotes. Only use quotes from published, verifiable sources. Placeholder quotes damage credibility more than no quotes at all. Build social proof by encouraging early users to share results publicly, then reference those real posts.
+
## Red Flags
- {issues that could undermine this positioning}
@@ -230,6 +242,33 @@ For [target customer] who [need/opportunity], [product] is a [category] that [ke
## Elevator Pitch (30 seconds)
{Conversational version of the positioning — what you'd say at a dinner party}
+## Tagline Candidates
+
+| Tagline | Angle | Best For | Possible Misread |
+|---------|-------|----------|-----------------|
+| {tagline 1} | {angle} | {context} | {how could a reader misinterpret this?} |
+| {tagline 2} | {angle} | {context} | {possible objection or wrong reading} |
+
+For each tagline, actively ask: "What could a skeptical reader think when reading this? What objection does it trigger?" If the misread is serious (e.g., sounds condescending, makes an assumption about the reader's situation, or positions in the wrong category), flag it and suggest a safer alternative.
+
+## One-Liner Variants
+
+Provide context-specific versions:
+- **For GitHub README:** {lead with open-source, end with free}
+- **For marketplace listing:** {lead with what user can DO, list deliverables}
+- **For social media:** {hook + transformation + differentiator}
+- **For elevator pitch:** {conversational, 30 seconds}
+
+## Freemium Positioning (if applicable)
+
+If the product has or plans a freemium model:
+
+**Free tier message:** {how to communicate that free is complete, not limited}
+**Premium tier message:** {how to communicate premium extends, not unlocks}
+**Upgrade trigger:** {natural moment when user would want premium}
+
+Anti-pattern: never make the free tier feel "incomplete" to push premium. The free tier should deliver full value for its scope. Premium adds a different scope (e.g., strategy vs. execution), not "more of the same."
+
## Validation Notes
- Onliness Test: {Pass/Fail + notes}
- Moore Template: {Pass/Fail + notes}
@@ -307,3 +346,68 @@ For [target customer] who [need/opportunity], [product] is a [category] that [ke
## Sources
- {key sources with tier ratings}
```
+
+### messaging-implications.md
+
+```markdown
+# Messaging Implications: {product}
+*Skill: startup-positioning | Generated: {date}*
+
+## Messaging Hierarchy
+
+What to communicate first, second, third. Every piece of copy should follow this priority:
+
+1. {Primary message — the outcome, what the user gets}
+2. {Secondary — time/effort, how fast or easy}
+3. {Tertiary — key differentiator}
+4. {Fourth — cost/access}
+5. {Fifth — specific deliverables or features}
+6. {Sixth — value anchor or comparison}
+
+Not every piece of copy needs all levels. But when present, they should appear in this order.
+
+## Category Label
+
+**Always use:** "{exact category phrase}"
+
+Use this exact phrase consistently across: website, GitHub, marketplace, social bios, README.
+
+## Value Anchor
+
+**"{value anchor phrase}"** — used in supporting copy to set perceived value. This is NOT the category label. The category describes WHAT it is. The value anchor describes WHAT IT'S WORTH.
+
+Where to use: body copy, comparison sections, pricing context.
+Where NOT to use: headlines, category descriptions, taglines (unless carefully tested).
+
+## Customer Language vs. Category Language
+
+| Customer says (use as verbs) | Category says (use as nouns/outcomes) |
+|------------------------------|--------------------------------------|
+| {e.g., "validate my idea"} | {e.g., "validated strategy"} |
+
+Bridge in copy: use customer verbs with category nouns.
+
+## Words to Use / Avoid
+
+| Use | Instead of | Why |
+|-----|-----------|-----|
+| {preferred term} | {avoided term} | {reason from positioning} |
+
+## Social Proof Guidelines
+
+Do not fabricate or pre-write social proof. Only use quotes from published, verifiable sources. Placeholder quotes damage credibility more than no quotes at all. If no real social proof exists yet, omit the section entirely and note it as a gap to fill.
+
+## Freemium Positioning (if applicable)
+
+**Free tier message:** {how to communicate that free is complete, not limited}
+**Premium tier message:** {how to communicate premium extends, not unlocks}
+**Upgrade trigger:** {natural moment when user would want premium}
+
+Anti-pattern: never make the free tier feel "incomplete" to push premium. The free tier should deliver full value for its scope. Premium adds a different scope (e.g., strategy vs. execution), not "more of the same."
+
+## Red Flags
+- {messaging risks}
+
+## Sources
+- {key sources}
+```