AI agent skills for startup validation, competitive intelligence, and planning
ai-agentsbattle-cardsclaude-codeclaude-skillscompetitive-analysiscompetitive-intelligencemarket-researchpricing-analysisstartupstartup-validation
fix: apply cross-skill audit fixes (P1-P6, M1-M5, CS1-CS6, N1-N16)
Ferdinando Bonsegna4a700362de06
diff --git a/.gitignore b/.gitignoreindex 0df9bea..40dc634 100644--- a/.gitignore+++ b/.gitignore@@ -17,6 +17,8 @@ eval_set.json# Internal planningtodo.md+GUIDELINES.md+startup-positioning-fixes.md# Local skills.agents/diff --git a/CLAUDE.md b/CLAUDE.mdindex 27647ee..d70e4c4 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -26,7 +26,7 @@ startup-skill/ # Plugin namespace (startup:*)├── .claude-plugin/│ └── marketplace.json # Plugin definition (name must be "startup")├── startup-design/ # Skill: startup:startup-design-│ ├── SKILL.md # Main skill file (~495 lines, 8 phases)+│ ├── SKILL.md # Main skill file (~522 lines, 8 phases)│ └── references/ # Supporting documents loaded on demand│ ├── research-principles.md│ ├── research-wave-1-market.md@@ -36,15 +36,16 @@ startup-skill/ # Plugin namespace (startup:*)│ ├── research-synthesis.md│ └── frameworks.md├── startup-competitors/ # Skill: startup:startup-competitors-│ ├── SKILL.md # Main skill file (~190 lines, 3 waves)+│ ├── SKILL.md # Main skill file (~210 lines, 3 waves)│ └── references/│ ├── research-principles.md│ ├── research-wave-1-profiles-pricing.md│ ├── research-wave-2-sentiment-mining.md│ ├── research-wave-3-gtm-signals.md-│ └── research-synthesis.md+│ ├── research-synthesis.md+│ └── honesty-protocol.md├── startup-positioning/ # Skill: startup:startup-positioning-│ ├── SKILL.md # Main skill file (~220 lines, 2 waves)+│ ├── SKILL.md # Main skill file (~240 lines, 2 waves)│ └── references/│ ├── research-principles.md│ ├── research-wave-1-alternatives.mddiff --git a/startup-competitors/SKILL.md b/startup-competitors/SKILL.mdindex d9b9d76..8b679d1 100644--- a/startup-competitors/SKILL.md+++ b/startup-competitors/SKILL.md@@ -63,6 +63,8 @@ Don't over-interview. If the user gives a clear description upfront, skip straigSave to `{project-name}/intake.md` — a brief summary of the product, market, and known competitors. If built on startup-design data, note the source files used. The project name should be derived from the product/market (kebab-case, e.g., `ai-email-assistant`).+Create `{project-name}/PROGRESS.md` with: project name, skill name (`startup-competitors`), start date, language, research mode (Live / Knowledge-Based), and a phase checklist. Update it after each phase completes. If PROGRESS.md already exists from a previous session, resume from the last incomplete phase.+---## Phase 2: Research@@ -116,7 +118,7 @@ Two agents (or two sequential blocks):## Phase 3: Synthesis-> **Reference:** Read `references/synthesis-battle-cards.md` for synthesis protocol and battle card template.+> **Reference:** Read `references/research-synthesis.md` for synthesis protocol and battle card template.After all waves complete, synthesize raw findings into strategic deliverables. This step creates the real value — it's not reporting, it's pattern-matching across data sources.@@ -178,14 +180,19 @@ Keep raw research files in `{project-name}/raw/` for reference:## Honesty Protocol-Competitive intelligence is only useful if it's honest. These rules are non-negotiable:+> **Reference:** Read `references/honesty-protocol.md` for full protocol and anti-pattern details.++Competitive intelligence is only useful if it's honest. Core rules apply (label claims, quantify, declare gaps), plus competitive-intelligence-specific additions:1. **No cheerleading.** If a competitor is objectively better at something, say so. Battle cards that ignore competitor strengths are useless in real sales conversations.-2. **Label claims.** Use **[Data]**, **[Estimate]**, **[Assumption]** tags. Never present guesses as facts.+2. **Label claims.** Use **[Data]**, **[Estimate]**, **[Assumption]**, **[Opinion]** tags. Never present guesses as facts.3. **Quantify.** "$12M ARR growing 40% YoY" not "they're growing fast."4. **Date everything.** Flag data older than 12 months.5. **Declare gaps.** "DATA GAP: Could not find reliable data on [X]" is always better than fabrication.6. **Surface red flags.** If the competitive landscape looks brutal, say so directly.+7. **Challenge confirmation bias.** When research confirms what the founder already believes, probe deeper. Look for disconfirming evidence.++See `references/honesty-protocol.md` for the full anti-pattern table (6 entries) and detailed protocol.---@@ -193,10 +200,11 @@ Competitive intelligence is only useful if it's honest. These rules are non-negoRead only what you need for the current phase.-| File | When to Read | Purpose |-|------|-------------|---------|-| `research-principles.md` | Before starting Phase 2 | Source quality, cross-referencing, data gaps |-| `research-wave-1-profiles-pricing.md` | When running Wave 1 | Agent templates for profiles + pricing |-| `research-wave-2-sentiment-mining.md` | When running Wave 2 | Agent templates for review + forum mining |-| `research-wave-3-gtm-signals.md` | When running Wave 3 | Agent templates for GTM + strategic signals |-| `research-synthesis.md` | After all waves complete | How to synthesize + battle card template |+| File | When to Read | ~Lines | Purpose |+|------|-------------|--------|---------|+| `honesty-protocol.md` | Start of session | ~72 | Full honesty protocol with anti-patterns |+| `research-principles.md` | Before starting Phase 2 | ~54 | Source quality, cross-referencing, data gaps |+| `research-wave-1-profiles-pricing.md` | When running Wave 1 | ~186 | Agent templates for profiles + pricing |+| `research-wave-2-sentiment-mining.md` | When running Wave 2 | ~189 | Agent templates for review + forum mining |+| `research-wave-3-gtm-signals.md` | When running Wave 3 | ~192 | Agent templates for GTM + strategic signals |+| `research-synthesis.md` | After all waves complete | ~231 | How to synthesize + battle card template |diff --git a/startup-competitors/references/honesty-protocol.md b/startup-competitors/references/honesty-protocol.mdnew file mode 100644index 0000000..c6d7f88--- /dev/null+++ b/startup-competitors/references/honesty-protocol.md@@ -0,0 +1,72 @@+# Radical Honesty Protocol++This skill exists to help founders make good decisions — not to feel good. An AI that cheerleads every idea is actively harmful: it wastes the founder's time, money, and emotional energy. These principles are non-negotiable and apply to every phase.++## Tell the truth, even when it's uncomfortable++- If the market is too small, say so directly. Don't soften "$12M and shrinking" into "room for a focused player."+- If the idea has a fatal flaw, name it up front. Don't bury it in a list of minor risks.+- If the founder's assumptions contradict research, flag it explicitly: "You assumed X, but the data shows Y."+- Challenge "everyone needs this" (who specifically?), "there's no competition" (there's always competition, even if it's doing nothing), and unsupported market claims.+- Never use vague positive language to avoid delivering bad news. Replace "interesting opportunity" with the specific finding.++## Separate facts from opinions++- Label every major claim with its basis:+ - **[Data]** — sourced finding with citation+ - **[Estimate]** — calculated projection with stated assumptions+ - **[Assumption]** — unverified belief that needs testing+ - **[Opinion]** — your analytical judgment+- When data is missing or weak, say so.+- Never present estimates as facts.+- A confident-sounding fabrication is worse than an honest "I don't know."++## Surface flags proactively++In every output file, include a **Flags** section at the end:++- **Red Flags** — Issues that could undermine the competitive analysis or the business.+- **Yellow Flags** — Concerns that need investigation or monitoring.++If there are no flags, write "No flags identified" — don't skip the section.++## Challenge the founder's assumptions++Don't just accept what the user says at face value:+- Ask "What evidence do you have for that?" when the founder claims competitive advantages+- Push back on "we have no competitors" — there's always competition, even doing nothing+- Question "we're better at everything" — no product wins on every dimension+- When the founder dismisses a competitor, test that dismissal against data++## Competitive Intelligence-Specific Rules++1. **Acknowledge competitor strengths.** Battle cards that ignore competitor strengths are useless in real sales conversations. If a competitor is objectively better at something, say so directly. The goal is to help the founder win deals, not feel good about their product.++2. **Challenge confirmation bias.** When research confirms what the founder already believes about a competitor, probe deeper. Confirmation bias is the #1 enemy of competitive intelligence. Look for disconfirming evidence.++3. **Don't cherry-pick reviews.** When mining customer sentiment, present the full picture — positive AND negative. Three angry Reddit posts don't mean a product is failing if it has 4.5 stars on G2 with 500 reviews. Represent sentiment proportionally.++4. **Flag intelligence gaps honestly.** If you couldn't find pricing, revenue, or traction data for a competitor, say so. A blank cell is better than a guess. Founders make resource allocation decisions based on competitive intelligence — fabricated data leads to bad strategy.++5. **Rate competitor threat honestly.** The final report must include an honest threat assessment per competitor:+ - **High threat** — Strong product, growing fast, well-funded, overlapping target+ - **Medium threat** — Competitive on some dimensions, gaps on others+ - **Low threat** — Weak product, stagnant, or targeting different segment+ Don't inflate threats to create urgency or deflate them to comfort the founder.++## Competitive Intelligence Anti-Patterns++| Anti-Pattern | What It Looks Like | What to Say |+|---|---|---|+| Cherry-picking weaknesses | Only listing competitor flaws | "What are they actually good at? Your sales team will face this in every deal." |+| Dismissing competitors | "They're not real competition" | "Their customers chose them over the alternatives. Why? What job are they doing well?" |+| Confirmation bias | Only finding data that confirms existing beliefs | "Let me look for evidence that contradicts this. What if we're wrong about [X]?" |+| Outdated intelligence | Using 2-year-old data for a fast-moving market | "This data is from {date}. The landscape may have shifted. Flag as potentially outdated." |+| Vanity comparisons | Comparing your best feature to their worst | "Compare apples to apples. Where do they win on dimensions that matter to buyers?" |+| Ignoring status quo | Not treating 'doing nothing' as competition | "Your biggest competitor might be inertia. What triggers someone to actually switch?" |++## Ground rules++- **Ground in evidence.** Every competitive claim should trace to research findings.+- **Make it actionable.** Intelligence that can't inform strategy is worthless.+- **No fabrication.** If data not found, say so.diff --git a/startup-competitors/references/research-synthesis.md b/startup-competitors/references/research-synthesis.mdindex 304ef19..0838901 100644--- a/startup-competitors/references/research-synthesis.md+++ b/startup-competitors/references/research-synthesis.md@@ -37,7 +37,7 @@ Structure:```markdown# Competitive Intelligence Report: {market/product}-*Generated: {date}*+*Skill: startup-competitors | Generated: {date}*## Executive Summary{5 sentences max: market concentration, key finding, biggest opportunity, biggest risk, overall assessment}@@ -53,6 +53,9 @@ Structure:|-----------|-------|---------|----------|----------|--------|| ... | ... | ... | ... | ... | H/M/L |+## Adjacent Solutions & Substitutes+{Broader platforms, manual alternatives, and tools from neighboring categories that compete for the same budget or job. Include: what job they solve, why buyers consider them, and how they compare to direct competitors.}+## Strategic OpportunitiesFor each opportunity:### Opportunity: {name}diff --git a/startup-competitors/references/research-wave-1-profiles-pricing.md b/startup-competitors/references/research-wave-1-profiles-pricing.mdindex 0866685..d04feac 100644--- a/startup-competitors/references/research-wave-1-profiles-pricing.md+++ b/startup-competitors/references/research-wave-1-profiles-pricing.md@@ -1,4 +1,4 @@-# Wave A: Competitor Profiles + Pricing Intelligence+# Wave 1: Competitor Profiles + Pricing IntelligenceRead `research-principles.md` first.diff --git a/startup-competitors/references/research-wave-2-sentiment-mining.md b/startup-competitors/references/research-wave-2-sentiment-mining.mdindex 5ae3f5f..41cc56c 100644--- a/startup-competitors/references/research-wave-2-sentiment-mining.md+++ b/startup-competitors/references/research-wave-2-sentiment-mining.md@@ -1,4 +1,4 @@-# Wave B: Customer Sentiment Mining+# Wave 2: Customer Sentiment MiningRead `research-principles.md` first.diff --git a/startup-competitors/references/research-wave-3-gtm-signals.md b/startup-competitors/references/research-wave-3-gtm-signals.mdindex a27c2a2..85b8c57 100644--- a/startup-competitors/references/research-wave-3-gtm-signals.md+++ b/startup-competitors/references/research-wave-3-gtm-signals.md@@ -1,4 +1,4 @@-# Wave C: GTM & Strategic Signals+# Wave 3: GTM & Strategic SignalsRead `research-principles.md` first.diff --git a/startup-design/SKILL.md b/startup-design/SKILL.mdindex e6f3be1..9c508a5 100644--- a/startup-design/SKILL.md+++ b/startup-design/SKILL.md@@ -174,30 +174,30 @@ Phase 3 requires WebSearch. In Claude Code, the tool is always available — if### Research Waves**Wave 1: Market Landscape** (3 agents in parallel, or 3 sequential research blocks)-- 1A: Market Sizing & Economics — TAM/SAM/SOM, unit economics benchmarks, market headwinds-- 1B: Industry Trends & Timing — tech trends, investment/M&A activity, behavioral shifts, expert predictions-- 1C: Regulatory & Compliance — current regulations, data privacy, upcoming changes, compliance costs- *(Skip 1C if the startup has no regulatory exposure)*+- A1: Market Sizing & Economics — TAM/SAM/SOM, unit economics benchmarks, market headwinds+- A2: Industry Trends & Timing — tech trends, investment/M&A activity, behavioral shifts, expert predictions+- A3: Regulatory & Compliance — current regulations, data privacy, upcoming changes, compliance costs+ *(Skip A3 if the startup has no regulatory exposure)*Complete Wave 1 before starting Wave 2. Pass key findings as context.**Wave 2: Competitive Analysis** (3 agents in parallel, or 3 sequential research blocks)-- 2A: Direct Competitor Deep-Dives — full profiles on 5-8 competitors (product, pricing, funding, traction, strengths, weaknesses)-- 2B: Indirect Competitors & Substitutes — alternative approaches, platform risk, switching costs-- 2C: Competitor Go-to-Market — how competitors acquire customers, channel analysis, content strategy+- B1: Direct Competitor Deep-Dives — full profiles on 5-8 competitors (product, pricing, funding, traction, strengths, weaknesses)+- B2: Indirect Competitors & Substitutes — alternative approaches, platform risk, switching costs+- B3: Competitor Go-to-Market — how competitors acquire customers, channel analysis, content strategyComplete Wave 2 before starting Wave 3. Pass competitor list and GTM findings as context.**Wave 3: Customer & Demand** (3 agents in parallel, or 3 sequential research blocks)-- 3A: Customer Voice & Pain Points — Reddit, forums, reviews mining with verbatim quotes, pain hierarchy, language map-- 3B: Demand Signals & Market Validation — search trends, pricing intelligence, Product Hunt signals, WTP evidence-- 3C: Target Audience Profiling — personas, buying behavior, decision-making process, where to reach them+- C1: Customer Voice & Pain Points — Reddit, forums, reviews mining with verbatim quotes, pain hierarchy, language map+- C2: Demand Signals & Market Validation — search trends, pricing intelligence, Product Hunt signals, WTP evidence+- C3: Target Audience Profiling — personas, buying behavior, decision-making process, where to reach themComplete Wave 3 before starting Wave 4.**Wave 4: Distribution & Partnerships** (2 agents in parallel, or 2 sequential research blocks)-- 4A: Distribution Channel Deep-Dive — channel ranking by ROI, SEO opportunity, partnership opportunities, first 90 days plan-- 4B: Geographic & Market Entry — beachhead market recommendation, entry barriers, expansion path+- D1: Distribution Channel Deep-Dive — channel ranking by ROI, SEO opportunity, partnership opportunities, first 90 days plan+- D2: Geographic & Market Entry — beachhead market recommendation, entry barriers, expansion path### Raw → Synthesized@@ -510,13 +510,13 @@ The `references/` directory contains supporting documentation. Read only what yo| File | When to Read | Lines ||------|-------------|-------|-| `output-guidelines.md` | At the start of every session (once) | ~70 |-| `honesty-protocol.md` | At the start of every session (once) | ~80 |-| `research-principles.md` | Before starting Phase 3 (once) | ~60 |-| `research-wave-1-market.md` | When spawning Wave 1 agents | ~130 |-| `research-wave-2-competitors.md` | When spawning Wave 2 agents | ~170 |-| `research-wave-3-customers.md` | When spawning Wave 3 agents | ~170 |-| `research-wave-4-distribution.md` | When spawning Wave 4 agents | ~110 |-| `research-synthesis.md` | After all waves complete, before writing final files | ~90 |-| `frameworks.md` | During Phase 4 (Strategy) and Phase 6 (Product) | ~110 |+| `output-guidelines.md` | At the start of every session (once) | ~78 |+| `honesty-protocol.md` | At the start of every session (once) | ~69 |+| `research-principles.md` | Before starting Phase 3 (once) | ~54 |+| `research-wave-1-market.md` | When spawning Wave 1 agents | ~206 |+| `research-wave-2-competitors.md` | When spawning Wave 2 agents | ~220 |+| `research-wave-3-customers.md` | When spawning Wave 3 agents | ~233 |+| `research-wave-4-distribution.md` | When spawning Wave 4 agents | ~132 |+| `research-synthesis.md` | After all waves complete, before writing final files | ~104 |+| `frameworks.md` | During Phase 4 (Strategy), Phase 6 (Product), and Phase 8 (Validation) | ~110 || `industry-benchmarks.md` | During Phase 7 (Financial) | ~80 |diff --git a/startup-design/references/research-synthesis.md b/startup-design/references/research-synthesis.mdindex 91f05f1..601ae5a 100644--- a/startup-design/references/research-synthesis.md+++ b/startup-design/references/research-synthesis.md@@ -1,6 +1,6 @@# Research Synthesis Protocol-After ALL waves complete (8-11 agents), synthesize the raw findings into polished deliverables. This step creates the real analytical value — it's not copying, it's connecting.+After ALL waves complete (10-11 agents, depending on whether A3/Regulatory was skipped), synthesize the raw findings into polished deliverables. This step creates the real analytical value — it's not copying, it's connecting.## How to Synthesize@@ -70,6 +70,26 @@ Structure:- **Timing scorecard:** is now the right time? Rate: tailwinds vs. headwinds- **Data gaps**+### `01-discovery/confidence-dashboard.md`+Synthesize from: ALL raw files across all waves.++Structure:+- **Overview** — How much of the analysis rests on solid ground vs. thin ice+- **Claim-level confidence** table:++| Claim | Source Tier | # Corroborating Sources | Confidence | Data Age |+|-------|-----------|------------------------|------------|----------|+| {major claim from research} | 1/2/3 | {count} | High/Medium/Low | {date or range} |++- **Highest confidence findings** — Claims backed by multiple Tier 1 sources+- **Lowest confidence findings** — Claims based on single sources, inferred data, or old information+- **Critical unknowns** — Things we don't know that could change the strategy+- **Recommendations** — What the founder should verify first, and how++This file helps the founder understand where they're standing on solid ground vs. making decisions based on weak data. It's the meta-layer above the other 4 deliverables.++---+## Cross-Document ConnectionsAfter writing all 4 files, add a "Strategic Connections" section at the end of each that links to insights from the other documents. For example:diff --git a/startup-design/references/research-wave-1-market.md b/startup-design/references/research-wave-1-market.mdindex ee37a4c..ff473be 100644--- a/startup-design/references/research-wave-1-market.md+++ b/startup-design/references/research-wave-1-market.md@@ -4,7 +4,7 @@ Read `research-principles.md` first for cross-cutting rules on source quality, c----## Agent 1A: Market Sizing & Economics+## Agent A1: Market Sizing & Economics```Research task: Deep market sizing for {industry/product category}@@ -75,7 +75,7 @@ Save to: {project-name}/01-discovery/raw/market-size.md----## Agent 1B: Industry Trends & Timing+## Agent A2: Industry Trends & Timing```Research task: Industry trends, timing signals, and future trajectory for {industry}@@ -143,7 +143,7 @@ Save to: {project-name}/01-discovery/raw/trends.md----## Agent 1C: Regulatory & Compliance Landscape+## Agent A3: Regulatory & Compliance LandscapeSkip this agent if the startup has no obvious regulatory exposure. When in doubt, run it — better to discover regulatory requirements early than late.diff --git a/startup-design/references/research-wave-2-competitors.md b/startup-design/references/research-wave-2-competitors.mdindex 2df557d..34fb276 100644--- a/startup-design/references/research-wave-2-competitors.md+++ b/startup-design/references/research-wave-2-competitors.md@@ -4,7 +4,7 @@ Read `research-principles.md` first. Wave 2 agents receive findings from Wave 1----## Agent 2A: Direct Competitor Deep-Dives+## Agent B1: Direct Competitor Deep-Dives```Research task: Deep analysis of direct competitors for {product description}@@ -96,12 +96,12 @@ Save to: {project-name}/01-discovery/raw/direct-competitors.md----## Agent 2B: Indirect Competitors & Substitutes+## Agent B2: Indirect Competitors & Substitutes```Research task: Indirect competitors, substitutes, and alternative approaches for {problem}Context: We're designing a startup that {one-sentence description}.-Direct competitors found: {list from Agent 2A if available, otherwise "to be determined"}+Direct competitors found: {list from Agent B1 if available, otherwise "to be determined"}RESEARCH PROTOCOL:@@ -161,12 +161,12 @@ Save to: {project-name}/01-discovery/raw/indirect-competitors.md----## Agent 2C: Competitor Go-to-Market Analysis+## Agent B3: Competitor Go-to-Market Analysis```Research task: How competitors in {product category} acquire and retain customersContext: We're designing a startup that {one-sentence description}.-Key competitors: {list top 3-5 from Agent 2A}+Key competitors: {list top 3-5 from Agent B1}RESEARCH PROTOCOL:diff --git a/startup-design/references/research-wave-3-customers.md b/startup-design/references/research-wave-3-customers.mdindex ab59f59..ed27723 100644--- a/startup-design/references/research-wave-3-customers.md+++ b/startup-design/references/research-wave-3-customers.md@@ -4,7 +4,7 @@ Read `research-principles.md` first. Wave 3 agents receive competitor findings f----## Agent 3A: Customer Voice & Pain Points+## Agent C1: Customer Voice & Pain Points```Research task: Deep customer research — real voices discussing {problem}@@ -82,7 +82,7 @@ Save to: {project-name}/01-discovery/raw/customer-voice.md----## Agent 3B: Demand Signals & Market Validation+## Agent C2: Demand Signals & Market Validation```Research task: Quantitative demand signals for {product category}@@ -158,7 +158,7 @@ Save to: {project-name}/01-discovery/raw/demand-signals.md----## Agent 3C: Target Audience Profiling+## Agent C3: Target Audience Profiling```Research task: Deep target audience research for {customer description}diff --git a/startup-design/references/research-wave-4-distribution.md b/startup-design/references/research-wave-4-distribution.mdindex f4de9bc..641b5f6 100644--- a/startup-design/references/research-wave-4-distribution.md+++ b/startup-design/references/research-wave-4-distribution.md@@ -4,13 +4,13 @@ Read `research-principles.md` first. Wave 4 agents receive all prior wave findin----## Agent 4A: Distribution Channel Deep-Dive+## Agent D1: Distribution Channel Deep-Dive```Research task: Viable distribution channels for {product category} targeting {customer type}Context: We're designing a startup that {one-sentence description}.-Competitor GTM findings: {summary from Agent 2C}-Target audience: {summary from Agent 3C}+Competitor GTM findings: {summary from Agent B3}+Target audience: {summary from Agent C3}RESEARCH PROTOCOL:@@ -84,7 +84,7 @@ Save to: {project-name}/01-discovery/raw/channels.md----## Agent 4B: Geographic & Market Entry Analysis+## Agent D2: Geographic & Market Entry Analysis```Research task: Geographic and market entry analysis for {product} in {target geography}diff --git a/startup-positioning/SKILL.md b/startup-positioning/SKILL.mdindex 2424741..8bfd262 100644--- a/startup-positioning/SKILL.md+++ b/startup-positioning/SKILL.md@@ -70,6 +70,8 @@ Don't over-interview. If the user gives a clear description upfront, move to resSave to `{project-name}/intake.md` — a brief summary of the product, problem, alternatives, and customers. If built on prior session data, note the source files used. Project name: kebab-case (e.g., `ai-email-assistant`).+Create `{project-name}/PROGRESS.md` with: project name, skill name (`startup-positioning`), start date, language, research mode (Live / Knowledge-Based), and a phase checklist. Update it after each phase completes. If PROGRESS.md already exists from a previous session, resume from the last incomplete phase.+---## Phase 2: Research@@ -85,7 +87,7 @@ Check if the `Agent` tool is available:### Web Search-This skill requires WebSearch for real data. If WebSearch is unavailable or denied, fall back to **Knowledge-Based Mode**: use training data, mark all findings with **[Knowledge-Based — verify independently]**, and reduce confidence ratings by one level.+This skill requires WebSearch for real data. If WebSearch is unavailable or denied, fall back to **Knowledge-Based Mode**: use training data, mark all findings with **[Knowledge-Based — verify independently]**, and reduce confidence ratings by one level. Note the mode in PROGRESS.md.> **Reference:** Read `references/research-principles.md` before starting any wave. It defines source quality tiers, cross-referencing rules, and how to handle data gaps.@@ -105,29 +107,39 @@ Two agents (or two sequential blocks):Two agents (or two sequential blocks):-**B1: Market Category Analysis** — Identify 2-3 candidate market categories. For each: what do buyers expect from this category, who are the leaders, what's the competitive dynamic, how mature is it? Apply Dunford's category types: head-to-head (existing category), big fish/small pond (subcategory), or category creation. Assess which frame makes your unique strengths matter most.+**B1: Market Category Analysis** — Identify 3-5 candidate market categories. For each: what do buyers expect from this category, who are the leaders, what's the competitive dynamic, how mature is it? Apply Dunford's category types: head-to-head (existing category), big fish/small pond (subcategory), or category creation. Assess which frame makes your unique strengths matter most.**B2: Trend & Timing Analysis** — Identify relevant trends: technology shifts, behavioral changes, regulatory moves. For each: is it real or hype, how does it affect buyer expectations, does it make your positioning stronger or weaker? Assess timing — are you early, on-time, or late to the trend? Only include trends that genuinely change how buyers evaluate solutions.---+### Post-Research Checkpoint++After both waves complete, before synthesis, briefly present what the research found to the user: the competitive alternative landscape (how many direct, adjacent, status quo), the strongest customer pains, and the most promising category candidates. Ask: "Does this align with your expectations? Anything to adjust before I synthesize the positioning?"++Keep it to one message — this is a quick alignment check, not a full report.++---+## Phase 3: Positioning Synthesis> **Reference:** Read `references/research-synthesis.md` for synthesis protocol and Dunford process details.-After both waves complete, build positioning through Dunford's 5+1 components **in order**. The sequence matters — each step builds on the previous.+After the checkpoint, build positioning through Dunford's 5+1 components **in order**. The sequence matters — each step builds on the previous.### The 5+1 Components1. **Competitive Alternatives** — From Wave 1. What would customers use if your product didn't exist? This is the anchor — positioning is always relative.-2. **Unique Attributes** — What do you have that the alternatives lack? Be specific and honest. Collaborate with the user here — they know capabilities you can't find in research. Features, architecture, team expertise, business model, speed — anything defensible.+2. **Unique Attributes** — What do you have that the alternatives lack? Be specific and honest. Features, architecture, team expertise, business model, speed — anything defensible.++ **⏸ PAUSE — User Input Required.** Present the research-derived attributes to the user. Ask them to confirm, add, or remove before proceeding to Value Themes. The founder knows capabilities that research can't surface.3. **Value Themes** — Translate each unique attribute into a customer outcome. Attribute → "so what?" → value. Group related attributes into 2-3 value themes. Use customer language from Wave 1's language map.4. **Best-Fit Customers** — From Wave 1 customer intelligence. Who cares most about your value themes? Define by characteristics that make them care, not demographics. These customers should be reachable, recognizable, and willing to pay.-5. **Market Category** — From Wave 2. Choose the category frame that makes your value obvious. Present 2-3 options with trade-offs. Recommend one. The right category triggers the right buyer expectations.+5. **Market Category** — From Wave 2. Choose the category frame that makes your value obvious. Present 3-5 options with trade-offs. Recommend one. The right category triggers the right buyer expectations.6. **Trend Overlay (optional)** — From Wave 2. Only include if a genuine trend makes your positioning stronger. Forced trend alignment is worse than none.@@ -136,9 +148,14 @@ After both waves complete, build positioning through Dunford's 5+1 components **Two stress tests before finalizing:**Neumeier Onliness Test:**++Basic form:+> "Our [product] is the only [category] that [differentiator]."++Extended form (6 elements — WHAT/HOW/WHO/WHERE/WHY/WHEN):> "Our [product] is the only [category] that [differentiator] for [target] who [need] in [context]."-If you can't fill this in convincingly, the positioning is too weak. Iterate.+If you can't fill the basic form convincingly — if "only" feels like a stretch — the positioning is too weak. Iterate.**Ries/Trout Mental Ladder:**- Is it simple enough to remember?@@ -168,14 +185,17 @@ If either test fails, revisit the 5+1 components. Don't ship weak positioning.- Your unique attributes vs. each alternative**`{project-name}/market-category-analysis.md`** — Category strategy:-- 2-3 candidate categories with buyer expectations+- 3-5 candidate categories with buyer expectations- Category type assessment (head-to-head / subcategory / creation)- Recommendation with reasoning-- Risk assessment for chosen category+- Implementation (category label, tagline direction, buyer expectation alignment)+- Red flags and yellow flags### Raw Data-Keep raw research files in `{project-name}/raw/` for reference:+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.++Raw research files:- `alternative-mapping.md`- `customer-intelligence.md`- `market-categories.md`@@ -210,11 +230,11 @@ See `references/honesty-protocol.md` for the full anti-pattern table (7 entries)Read only what you need for the current phase.-| File | When to Read | Purpose |-|------|-------------|---------|-| `research-principles.md` | Before starting Phase 2 | Source quality, cross-referencing, data gaps |-| `research-wave-1-alternatives.md` | When running Wave 1 | Agent templates for alternatives + customer intel |-| `research-wave-2-market-frame.md` | When running Wave 2 | Agent templates for categories + trends |-| `research-synthesis.md` | After both waves complete | Synthesis protocol, Dunford process, validation tests |-| `frameworks.md` | During Phase 3 | Dunford/Moore/Neumeier/JTBD/Ries reference |-| `honesty-protocol.md` | Start of session | Full honesty protocol with anti-patterns |+| File | When to Read | ~Lines | Purpose |+|------|-------------|--------|---------|+| `honesty-protocol.md` | Start of session | ~73 | Full honesty protocol with anti-patterns |+| `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 |+| `frameworks.md` | During Phase 3 | ~133 | Dunford/Moore/Neumeier/JTBD/Ries reference |diff --git a/startup-positioning/references/frameworks.md b/startup-positioning/references/frameworks.mdindex fa5e449..1142ec4 100644--- a/startup-positioning/references/frameworks.md+++ b/startup-positioning/references/frameworks.md@@ -14,9 +14,9 @@ Positioning defines how your product is the best in the world at providing somet2. **Unique Attributes** — What do you have that the alternatives don't? Be specific and factual. Not "better UX" but "drag-and-drop workflow builder that requires zero code." Capabilities, features, expertise, integrations, data, speed, etc.-3. **Value** — What do those attributes enable for the customer? Map each attribute to a customer benefit. Attributes are features; value is the outcome. "Drag-and-drop builder" → "Non-technical teams can build workflows without waiting for engineering."+3. **Value Themes** — What do those attributes enable for the customer? Map each attribute to a customer benefit. Attributes are features; value themes are outcomes. "Drag-and-drop builder" → "Non-technical teams can build workflows without waiting for engineering." Group related attributes into 2-3 themes.-4. **Target Customer** — Who cares the most about this value? The best customers are those for whom your unique value is critical, not just nice-to-have. Define by characteristics that make them care more than others.+4. **Best-Fit Customers** — Who cares the most about these value themes? The best customers are those for whom your unique value is critical, not just nice-to-have. Define by characteristics that make them care more than others.5. **Market Category** — The context you position your product in so the value is obvious. Three options:- **Existing category**: You're a better version of something people already buy (e.g., "CRM for real estate agents")@@ -40,8 +40,8 @@ Positioning defines how your product is the best in the world at providing somet- **Alternatives:** Only listing direct competitors. Miss the status quo — manual processes, spreadsheets, hiring someone, doing nothing. These are often the real competition.- **Attributes:** Listing features that alternatives also have. That is table stakes, not differentiation. If two competitors also have it, it is not unique.-- **Value:** Staying at the feature level instead of translating to outcomes. "AI-powered" is an attribute. "Get answers in seconds instead of hours" is value.-- **Target:** Too broad ("SMBs") or demographic ("25-34 year olds") instead of characteristic-based. Define by behaviors, situations, and needs that make them care more.+- **Value Themes:** Staying at the feature level instead of translating to outcomes. "AI-powered" is an attribute. "Get answers in seconds instead of hours" is a value theme.+- **Best-Fit Customers:** Too broad ("SMBs") or demographic ("25-34 year olds") instead of characteristic-based. Define by behaviors, situations, and needs that make them care more.- **Category:** Inventing a category nobody searches for. If customers cannot Google it, they cannot find you.---@@ -59,12 +59,12 @@ Positioning defines how your product is the best in the world at providing somet**Field definitions:**-- **Target customer** = Dunford's Best-Fit Customers+- **Target customer** = Dunford component 4: Best-Fit Customers- **Need** = The job to be done (from JTBD analysis)-- **Category** = Dunford's Market Category-- **Key benefit** = Dunford's Value Themes (pick the strongest)-- **Alternative** = Dunford's top Competitive Alternative-- **Differentiation** = Dunford's Unique Attributes (most defensible)+- **Category** = Dunford component 5: Market Category+- **Key benefit** = Dunford component 3: Value Themes (pick the strongest)+- **Alternative** = Dunford component 1: top Competitive Alternative+- **Differentiation** = Dunford component 2: Unique Attributes (most defensible)**Example:**diff --git a/startup-positioning/references/research-synthesis.md b/startup-positioning/references/research-synthesis.mdindex bf9df7a..89413c8 100644--- a/startup-positioning/references/research-synthesis.md+++ b/startup-positioning/references/research-synthesis.md@@ -132,7 +132,7 @@ If any test fails, iterate on the 5+1 components. Do not ship weak positioning.```markdown# Market Positioning: {product}-*Generated: {date}*+*Skill: startup-positioning | Generated: {date}*## Executive Summary{Positioning in 3 sentences: who you are, for whom, why you win.}@@ -144,10 +144,14 @@ If any test fails, iterate on the 5+1 components. Do not ship weak positioning.| Alternative | Type | Job Match | Where It Falls Short ||---|---|---|---|+> **Confidence:** High/Medium/Low — {reasoning}+## 2. Unique Attributes| Attribute | Evidence | Defensible? ||---|---|---|+> **Confidence:** High/Medium/Low — {reasoning}+## 3. Value Themes### Theme 1: {name}- **Attributes:** {which unique attributes drive this}@@ -157,19 +161,28 @@ If any test fails, iterate on the 5+1 components. Do not ship weak positioning.### Theme 2: {name}[same structure]+> **Confidence:** High/Medium/Low — {reasoning}+## 4. Best-Fit Customers**Profile:** {characteristics that predict high value and fast adoption}**Evidence:** {from customer intelligence}**Why they care more:** {what makes this value theme critical for them vs. others}+> **Confidence:** High/Medium/Low — {reasoning}+## 5. Market Category**Chosen category:** {name} ({type: existing / subcategory / new})**Why this frame:** {reasoning — how it makes unique value obvious}**Buyer expectations:** {what this category signals to buyers}**Risk:** {what expectations might work against you}+> **Confidence:** High/Medium/Low — {reasoning}+## 6. Trend Overlay{Trend and how it amplifies positioning — or "None. The positioning stands on its own."}+**Would the positioning work without this trend?** {Yes/No + reasoning. If No, the positioning is too trend-dependent — revisit.}++> **Confidence:** High/Medium/Low — {reasoning}## Positioning Strength Assessment| Component | Strength | Notes |@@ -198,7 +211,7 @@ If any test fails, iterate on the 5+1 components. Do not ship weak positioning.```markdown# Positioning Statements: {product}-*Generated: {date}*+*Skill: startup-positioning | Generated: {date}*## Moore Positioning StatementFor [target customer] who [need/opportunity], [product] is a [category] that [key benefit]. Unlike [primary alternative], our product [primary differentiation].@@ -228,7 +241,7 @@ For [target customer] who [need/opportunity], [product] is a [category] that [ke```markdown# Competitive Alternatives Map: {product}-*Generated: {date}*+*Skill: startup-positioning | Generated: {date}*## The Job to Be Done{Core job customers are hiring for}@@ -246,15 +259,29 @@ For [target customer] who [need/opportunity], [product] is a [category] that [ke| Alternative | What They Offer | Where You Win | Where They Win ||---|---|---|---|+## Switching Cost Analysis+| Alternative | Technical | Contractual | Emotional | Net Switching Barrier |+|---|---|---|---|---|+| {name} | H/M/L | H/M/L | H/M/L | {summary} |+## Key Positioning Insights- {what the alternative landscape tells us about positioning}++## Red Flags+- {issues in the competitive alternative landscape}++## Yellow Flags+- {concerns to monitor}++## Sources+- {key sources with tier ratings}```### market-category-analysis.md```markdown# Market Category Analysis: {product}-*Generated: {date}*+*Skill: startup-positioning | Generated: {date}*## Candidate Categories### {Category 1}: {type}@@ -268,5 +295,15 @@ For [target customer] who [need/opportunity], [product] is a [category] that [ke- **Tagline direction:** {how to frame it}- **Buyer expectation alignment:** {what expectations you meet, which you need to manage}-## Red Flags / Yellow Flags+## Red Flags+- {issues that could undermine the category choice}++## Yellow Flags+- {concerns to monitor}++## Data Gaps+- {what data is missing about category dynamics}++## Sources+- {key sources with tier ratings}```