startup-design

Name: startup-design
Author: ferdinandobons

381installs85forks

How to install startup-design?

ferdinandobons/startup-skill/startup-design

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

Installs into the current project.

Summary

Design, validate, and plan a startup from scratch. Covers market research, competitive analysis, business model, brand identity, product definition, financial projections, and validation experiments. Trigger when the user has a startup idea to explore, wants to validate a busines

Files · 1

View on GitHub

SKILL.md

1	# Startup Design
2
3	A structured, multi-phase skill that takes a startup idea from raw concept to validated design. It produces a complete set of markdown documents organized by domain, with built-in progress tracking so work survives session interruptions.
4
5	## How It Works
6
7	The process has 8 numbered phases executed sequentially, plus a Pre-Flight Check (Phase 0.5) and a Customer Discovery gate (Phase 3.7). Each phase produces output files and updates the progress tracker. If a session is interrupted, resume from the last completed checkpoint.
8
9	```
10	PRE-FLIGHT → INTAKE → BRAINSTORM → RESEARCH → [Research Gate] → CUSTOMER DISCOVERY → [Interview Gate] → STRATEGY → BRAND → PRODUCT → FINANCIAL → VALIDATION
11	```
12
13	### Modes
14
15	Full Mode (default): Execute all phases in order, including Pre-Flight and Customer Discovery. Best for thoroughly designing a startup from scratch.
16
17	Fast Track Mode: When the user says they want a "quick validation," "rapid assessment," or similar, or when time/budget is clearly limited, run a compressed version:
18	1. Phase 0.5 (Pre-Flight Check) — always run, takes 5 minutes
19	2. Phase 1 (Intake) — shortened to 1 round of questions; capture any prior customer conversations
20	3. Phase 2 (Brainstorm) — 3 variations instead of 5-8
21	4. Phase 3 (Research) — Wave 1 + Wave 2 only (skip customer voice and distribution deep-dives)
22	5. Phase 3.5 (Research Gate) — go/no-go checkpoint
23	6. Phase 3.7 (Customer Discovery) — if founder has 5+ prior conversations, document them; if not, run at least 3 interviews before proceeding
24	7. Phase 4 (Strategy) — Lean Canvas only
25	8. Skip Phase 5 (Brand) and Phase 6 (Product)
26	9. Phase 7 (Financial) — Revenue model only, Stage A (assumption-based), no full projections
27	10. Phase 8 (Validation) — Scorecard + top 3 experiments only
28
29	Fast Track produces fewer files but still gives the founder a clear go/no-go signal with evidence. Note in PROGRESS.md that Fast Track mode was used, so a future session can expand to full mode if the idea passes validation.
30
31	### Language
32
33	Default output language is English. If the user writes in another language or explicitly requests one, use that language for all outputs instead.
34
35	---
36
37	> Reference: Read `references/output-guidelines.md` once at the start. It defines the standard file header/footer (title, date, phase, confidence, flags), cross-phase referencing format, quality examples of good vs. bad output, and how to handle mid-process pivots.
38
39	## Phase 0: Resume Check
40
41	Before anything else, check if a `PROGRESS.md` file exists in the working directory (or a project subdirectory). 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]."
42
43	If no progress file exists, start from Phase 1.
44
45	---
46
47	## Phase 0.5: Pre-Flight Check
48
49	Before investing time in the full process, run a fast sanity check — 2-3 targeted searches, 5 minutes maximum. The goal is to surface any immediately disqualifying signals so the founder knows them upfront.
50
51	Run these three checks:
52
53	1. Dominant solution check — Does a well-funded, widely-adopted solution to this exact problem already exist? Search: `"{problem domain} software"`, `"{problem} tool site:producthunt.com"`, `"{problem} app reviews"`. If a clear market leader with 10k+ customers exists, flag it immediately — this is not a reason to stop, but the founder needs to know the competitive reality before starting.
54
55	2. Precedent failure check — Has a company tried this exact idea and failed publicly? Search: `"{startup idea} startup failed"`, `"{problem} startup shutdown"`, `"why {product category} failed"`. Prior failures are not disqualifying — they're learnings. But unknown prior failures are landmines.
56
57	3. Regulatory/legal instant kill — Is there an obvious legal reason this idea cannot exist? (E.g., specific financial regulations, data privacy laws in the target geography, licensing requirements.) A quick search prevents building toward a wall.
58
59	Output: A short message to the founder (3-5 bullet points max) with what was found. Use this format:
60
61	```
62	## Pre-Flight Check
63
64	✅ No dominant incumbent found — space appears open.
65	⚠️ [CompanyX] tried a similar approach in 2021 and shut down in 2023.
66	Key reason: [one sentence]. Worth understanding before proceeding.
67	✅ No obvious regulator

People who liked this also viewed

6 picks

Type

startup-design

381installs85forks

View on GitHub

How to install startup-design?

ferdinandobons/startup-skill/startup-design

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Startup Design
2
3	A structured, multi-phase skill that takes a startup idea from raw concept to validated design. It produces a complete set of markdown documents organized by domain, with built-in progress tracking so work survives session interruptions.
4
5	## How It Works
6
7	The process has 8 numbered phases executed sequentially, plus a Pre-Flight Check (Phase 0.5) and a Customer Discovery gate (Phase 3.7). Each phase produces output files and updates the progress tracker. If a session is interrupted, resume from the last completed checkpoint.
8
9	```
10	PRE-FLIGHT → INTAKE → BRAINSTORM → RESEARCH → [Research Gate] → CUSTOMER DISCOVERY → [Interview Gate] → STRATEGY → BRAND → PRODUCT → FINANCIAL → VALIDATION
11	```
12
13	### Modes
14
15	Full Mode (default): Execute all phases in order, including Pre-Flight and Customer Discovery. Best for thoroughly designing a startup from scratch.
16
17	Fast Track Mode: When the user says they want a "quick validation," "rapid assessment," or similar, or when time/budget is clearly limited, run a compressed version:
18	1. Phase 0.5 (Pre-Flight Check) — always run, takes 5 minutes
19	2. Phase 1 (Intake) — shortened to 1 round of questions; capture any prior customer conversations
20	3. Phase 2 (Brainstorm) — 3 variations instead of 5-8
21	4. Phase 3 (Research) — Wave 1 + Wave 2 only (skip customer voice and distribution deep-dives)
22	5. Phase 3.5 (Research Gate) — go/no-go checkpoint
23	6. Phase 3.7 (Customer Discovery) — if founder has 5+ prior conversations, document them; if not, run at least 3 interviews before proceeding
24	7. Phase 4 (Strategy) — Lean Canvas only
25	8. Skip Phase 5 (Brand) and Phase 6 (Product)
26	9. Phase 7 (Financial) — Revenue model only, Stage A (assumption-based), no full projections
27	10. Phase 8 (Validation) — Scorecard + top 3 experiments only
28
29	Fast Track produces fewer files but still gives the founder a clear go/no-go signal with evidence. Note in PROGRESS.md that Fast Track mode was used, so a future session can expand to full mode if the idea passes validation.
30
31	### Language
32
33	Default output language is English. If the user writes in another language or explicitly requests one, use that language for all outputs instead.
34
35	---
36
37	> Reference: Read `references/output-guidelines.md` once at the start. It defines the standard file header/footer (title, date, phase, confidence, flags), cross-phase referencing format, quality examples of good vs. bad output, and how to handle mid-process pivots.
38
39	## Phase 0: Resume Check
40
41	Before anything else, check if a `PROGRESS.md` file exists in the working directory (or a project subdirectory). 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]."
42
43	If no progress file exists, start from Phase 1.
44
45	---
46
47	## Phase 0.5: Pre-Flight Check
48
49	Before investing time in the full process, run a fast sanity check — 2-3 targeted searches, 5 minutes maximum. The goal is to surface any immediately disqualifying signals so the founder knows them upfront.
50
51	Run these three checks:
52
53	1. Dominant solution check — Does a well-funded, widely-adopted solution to this exact problem already exist? Search: `"{problem domain} software"`, `"{problem} tool site:producthunt.com"`, `"{problem} app reviews"`. If a clear market leader with 10k+ customers exists, flag it immediately — this is not a reason to stop, but the founder needs to know the competitive reality before starting.
54
55	2. Precedent failure check — Has a company tried this exact idea and failed publicly? Search: `"{startup idea} startup failed"`, `"{problem} startup shutdown"`, `"why {product category} failed"`. Prior failures are not disqualifying — they're learnings. But unknown prior failures are landmines.
56
57	3. Regulatory/legal instant kill — Is there an obvious legal reason this idea cannot exist? (E.g., specific financial regulations, data privacy laws in the target geography, licensing requirements.) A quick search prevents building toward a wall.
58
59	Output: A short message to the founder (3-5 bullet points max) with what was found. Use this format:
60
61	```
62	## Pre-Flight Check
63
64	✅ No dominant incumbent found — space appears open.
65	⚠️ [CompanyX] tried a similar approach in 2021 and shut down in 2023.
66	Key reason: [one sentence]. Worth understanding before proceeding.
67	✅ No obvious regulator

People who liked this also viewed

6 picks

Type