startup-positioning

Name: startup-positioning
Author: ferdinandobons

321installs85forks

How to install startup-positioning?

ferdinandobons/startup-skill/startup-positioning

$npx -y skills add ferdinandobons/startup-skill --skill startup-positioning

Installs into the current project.

Summary

Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test. Produces a complete positioning document, positioning statement, competitive alternatives map, and market category analysis. Use

Files · 1

View on GitHub

SKILL.md

1	# Startup Positioning
2
3	Market positioning strategy that produces a complete positioning document, Moore + Neumeier positioning statements, competitive alternatives map, and market category analysis. Built on April Dunford's framework, enriched with JTBD discovery and stress-tested with Neumeier's Onliness Test.
4
5	## How It Works
6
7	```
8	INTAKE → RESEARCH (2 sequential waves) → POSITIONING SYNTHESIS
9	```
10
11	The process: understand the product and its customers, research competitive alternatives and market context, then build positioning through Dunford's 5+1 components. Typical runtime: 10-15 minutes in Claude Code (parallel agents), 20-30 minutes in Claude.ai (sequential).
12
13	### Language
14
15	Default output language is English. If the user writes in another language or explicitly requests one, use that language for all outputs instead.
16
17	---
18
19	## Phase 0: Resume Check
20
21	Before anything else, check if a `PROGRESS.md` created by this skill exists in the working directory or a project subdirectory (the skill name field says `startup-positioning`). If it does, read it and resume from the last incomplete phase. Tell the user: "I found progress from a previous session. You completed [phases]. Picking up from [next phase]."
22
23	If no progress file exists — or the one found belongs to a different skill — start from Phase 1.
24
25	---
26
27	## Phase 1: Intake
28
29	Short and focused — 1-2 rounds of questions. The goal is enough context to research alternatives and build positioning.
30
31	### Check for Prior Work
32
33	Before asking questions, check if prior sessions have been completed. Look for these files in the working directory or subdirectories:
34
35	From startup-design:
36	- `00-intake/brief.md` — product description and context
37	- `01-discovery/competitor-landscape.md` — competitor profiles
38	- `01-discovery/target-audience.md` — customer personas, pain points
39	- `02-strategy/positioning.md` — initial positioning work
40
41	From startup-competitors:
42	- `intake.md` — product and market context
43	- `competitors-report.md` — strategic competitive analysis
44	- `battle-cards/` — per-competitor profiles
45	- `pricing-landscape.md` — pricing analysis
46
47	If these files exist, read them and use the data as a head start:
48	- Extract the product description, known competitors, and customer pain points
49	- Use competitor profiles and battle cards to seed the competitive alternatives map
50	- Pull any existing positioning work as a starting hypothesis to test, not a conclusion to keep
51	- Use customer language and pain points to inform JTBD discovery
52
53	Tell the user: "I found data from a previous session. I'll use it as a starting point for positioning analysis."
54
55	Skip redundant intake questions. Go straight to research if prior data is sufficient.
56
57	### What to Ask (if no prior data exists)
58
59	Round 1 — Core context:
60	- What's your product? (one sentence is fine)
61	- What problem does it solve and for whom?
62	- What do your customers do today instead of using you? (alternatives, workarounds, doing nothing)
63	- Who are your best existing customers? (if any — describe them, not demographics)
64
65	Round 2 — Sharpening (only if needed):
66	- How is your product different from the alternatives you mentioned?
67	- Have you tried positioning before? What didn't work?
68	- Are there competitors you're often compared to?
69
70	Don't over-interview. If the user gives a clear description upfront, move to research. The positioning process itself will surface what matters.
71
72	### Output
73
74	Save 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`).
75
76	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.
77
78	---
79
80	## Phase 1.5: Research De

People who liked this also viewed

6 picks

Type

startup-positioning

321installs85forks

View on GitHub

How to install startup-positioning?

ferdinandobons/startup-skill/startup-positioning

$npx -y skills add ferdinandobons/startup-skill --skill startup-positioning

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Startup Positioning
2
3	Market positioning strategy that produces a complete positioning document, Moore + Neumeier positioning statements, competitive alternatives map, and market category analysis. Built on April Dunford's framework, enriched with JTBD discovery and stress-tested with Neumeier's Onliness Test.
4
5	## How It Works
6
7	```
8	INTAKE → RESEARCH (2 sequential waves) → POSITIONING SYNTHESIS
9	```
10
11	The process: understand the product and its customers, research competitive alternatives and market context, then build positioning through Dunford's 5+1 components. Typical runtime: 10-15 minutes in Claude Code (parallel agents), 20-30 minutes in Claude.ai (sequential).
12
13	### Language
14
15	Default output language is English. If the user writes in another language or explicitly requests one, use that language for all outputs instead.
16
17	---
18
19	## Phase 0: Resume Check
20
21	Before anything else, check if a `PROGRESS.md` created by this skill exists in the working directory or a project subdirectory (the skill name field says `startup-positioning`). If it does, read it and resume from the last incomplete phase. Tell the user: "I found progress from a previous session. You completed [phases]. Picking up from [next phase]."
22
23	If no progress file exists — or the one found belongs to a different skill — start from Phase 1.
24
25	---
26
27	## Phase 1: Intake
28
29	Short and focused — 1-2 rounds of questions. The goal is enough context to research alternatives and build positioning.
30
31	### Check for Prior Work
32
33	Before asking questions, check if prior sessions have been completed. Look for these files in the working directory or subdirectories:
34
35	From startup-design:
36	- `00-intake/brief.md` — product description and context
37	- `01-discovery/competitor-landscape.md` — competitor profiles
38	- `01-discovery/target-audience.md` — customer personas, pain points
39	- `02-strategy/positioning.md` — initial positioning work
40
41	From startup-competitors:
42	- `intake.md` — product and market context
43	- `competitors-report.md` — strategic competitive analysis
44	- `battle-cards/` — per-competitor profiles
45	- `pricing-landscape.md` — pricing analysis
46
47	If these files exist, read them and use the data as a head start:
48	- Extract the product description, known competitors, and customer pain points
49	- Use competitor profiles and battle cards to seed the competitive alternatives map
50	- Pull any existing positioning work as a starting hypothesis to test, not a conclusion to keep
51	- Use customer language and pain points to inform JTBD discovery
52
53	Tell the user: "I found data from a previous session. I'll use it as a starting point for positioning analysis."
54
55	Skip redundant intake questions. Go straight to research if prior data is sufficient.
56
57	### What to Ask (if no prior data exists)
58
59	Round 1 — Core context:
60	- What's your product? (one sentence is fine)
61	- What problem does it solve and for whom?
62	- What do your customers do today instead of using you? (alternatives, workarounds, doing nothing)
63	- Who are your best existing customers? (if any — describe them, not demographics)
64
65	Round 2 — Sharpening (only if needed):
66	- How is your product different from the alternatives you mentioned?
67	- Have you tried positioning before? What didn't work?
68	- Are there competitors you're often compared to?
69
70	Don't over-interview. If the user gives a clear description upfront, move to research. The positioning process itself will surface what matters.
71
72	### Output
73
74	Save 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`).
75
76	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.
77
78	---
79
80	## Phase 1.5: Research De

People who liked this also viewed

6 picks

Type