1---
2name: organize-idea
3description: Create or organize a SaaS idea into the standard project structure. Use when the user says "new idea", "organize idea", or wants to set up/reorganize a project in ~/Ideas/. Works for both new and existing projects.
4---
5
6# Organize Idea
7
8Create or organize a SaaS project into the standard folder structure at `~/Ideas/<ProjectName>/`.
9
10## Safety Rules
11
12- **NEVER delete any files or folders**
13- **NEVER overwrite existing files**
14- When moving files, always verify the destination doesn't already have a file with the same name
15- If unsure where something belongs, leave it in place and tell the user
16- Show the user what you plan to move BEFORE moving anything and get confirmation
17
18## Folder Structure
19
20Every idea gets this structure. Create all folders that don't already exist. Folders are numbered so they sort in logical lifecycle order in Finder and file explorers:
21
22```
23<ProjectName>/
24├── 01 Idea/
25│ ├── 01a Problem Discovery/
26│ ├── 01b Market Research/
27│ ├── 01c Niche Selection/
28│ ├── 01d Competitor Analysis/
29│ └── 01e Opportunity Mapping/
30│
31├── 02 Validation/
32│ ├── 02a Customer Interviews/
33│ ├── 02b Landing Page Test/
34│ ├── 02c Waitlist/
35│ ├── 02d Pre Sales/
36│ └── 02e Demand Testing/
37│
38├── 03 Planning/
39│ ├── 03a Product Roadmap/
40│ ├── 03b Feature Prioritization/
41│ ├── 03c MVP Scope/
42│ ├── 03d Tech Stack/
43│ └── 03e Development Plan/
44│
45├── 04 Design/
46│ ├── 04a Wireframes/
47│ ├── 04b UI Design/
48│ ├── 04c UX Flows/
49│ ├── 04d Prototype/
50│ └── 04e Design System/
51│
52├── 05 Development/
53│ ├── 05a Frontend/
54│ ├── 05b Backend/
55│ ├── 05c APIs/
56│ ├── 05d Database/
57│ ├── 05e Authentication/
58│ └── 05f Integrations/
59│
60├── 06 Infrastructure/
61│ ├── 06a Cloud Hosting/
62│ ├── 06b DevOps/
63│ ├── 06c CI CD/
64│ ├── 06d Monitoring/
65│ └── 06e Security/
66│
67├── 07 Testing/
68│ ├── 07a Unit Testing/
69│ ├── 07b Integration Testing/
70│ ├── 07c Bug Fixing/
71│ ├── 07d Performance Testing/
72│ └── 07e Beta Testing/
73│
74├── 08 Launch/
75│ ├── 08a Landing Page/
76│ ├── 08b Product Hunt/
77│ ├── 08c Beta Users/
78│ ├── 08d Early Adopters/
79│ └── 08e Public Release/
80│
81├── 09 Acquisition/
82│ ├── 09a SEO Wins/
83│ ├── 09b Content Marketing/
84│ ├── 09c Social Media/
85│ ├── 09d Cold Email/
86│ ├── 09e Influencer Outreach/
87│ └── 09f Affiliate Marketing/
88│
89├── 10 Distribution/
90│ ├── 10a Directories/
91│ ├── 10b SaaS Marketplaces/
92│ ├── 10c Communities/
93│ ├── 10d Partnerships/
94│ └── 10e Integrations/
95│
96├── 11 Conversion/
97│ ├── 11a Sales Funnel/
98│ ├── 11b Free Trial/
99│ ├── 11c Freemium Model/
100│ ├── 11d Pricing Strategy/
101│ └── 11e Checkout Optimization/
102│
103├── 12 Revenue/
104│ ├── 12a Subscriptions/
105│ ├── 12b Upsells/
106│ ├── 12c Add-ons/
107│ ├── 12d Annual Plans/
108│ └── 12e Enterprise Deals/
109│
110├── 13 Analytics/
111│ ├── 13a User Tracking/
112│ ├── 13b Funnel Analysis/
113│ ├── 13c Cohort Analysis/
114│ ├── 13d KPI Dashboard/
115│ └── 13e A-B Testing/
116│
117├── 14 Retention/
118│ ├── 14a User Onboarding/
119│ ├── 14b Email Automation/
120│ ├── 14c Customer Support/
121│ ├── 14d Feature Adoption/
122│ └── 14e Churn Reduction/
123│
124├── 15 Growth/
125│ ├── 15a Referral Programs/
126│ ├── 15b Community Building/
127│ ├── 15c Product Led Growth/
128│ ├── 15d Viral Loops/
129│ └── 15e Expansion Strategy/
130│
131└── 16 Scaling/
132 ├── 16a Automation/
133 ├── 16b Hiring/
134 ├── 16c Systems/
135 ├── 16d Global Expansion/
136 └── 16e Exit Strategy/
137```
138
139## Steps
140
141### 1. Identify the project
142
143Ask for the project name if not provided. Set `BASE=~/Ideas/<ProjectName>`.
144
145### 2. Create the structure
146
147Run `mkdir -p` for every subfolder listed above. This is safe — it only creates what doesn't exist.
148
149### 3. If the project already had files, organize them
150
151Scan all existing files and folders at the root level and any non-standard subfolders (anything that doesn't match the numbered folder pattern). For each item:
152
153- Read the file or inspect the folder contents to understand what it is
154- Determine which category and subfolder it belongs in based on its content
155- **Common mappings:**
156 - Competitor docs, market analysis → `01 Idea/01d Competitor Analysis` or `01 Idea/01b Market Research`
157 - One-pagers, pitch decks, specs → `03 Planning/03c MVP Scope` or `03 Planning/03a Product Roadmap`
158 - Wireframes, mockups, Figma exports → `04 Design/04a Wireframes` or `04 Design/04b UI Design`
159 - Code repos, source files → `05 Development/` (appropriate subfolder)
160 - SEO content, blog posts → `09 Acquisition/09b Content Marketing` or `09 Acquisition/09a SEO Wins`
161 - Pricing docs → `11 Conversion/11d Pricing Strategy`
162 - User research, interview notes → `02 Validation/02a Customer Interviews`
163 - Launch checklists → `08 Launch/` (appropriate subfolder)
164 - Meeting notes, call transcripts → categorize by topic discussed
165 - Domain research → `01 Idea/01b Market Research`
166
167### 4. Present the plan
168
169Show the user a table of proposed moves:
170
171```
172| File/Folder | From | To |
173|--------------------------|-----------------------|---------------------------------------|
174| competitor-analysis.md | ./ | 01 Idea/01d Competitor Analysis/ |
175| pricing-v2.xlsx | ./docs/ | 11 Conversion/11d Pricing Strategy/ |
176```
177
178If any files are ambiguous, list them separately and ask the user where they should go.
179
180### 5. Execute after confirmation
181
182Only move files after the user confirms. Use `mv` for each file individually — no bulk operations.
183
184### 6. Report
185
186Show the final state: how many folders exist, how many files were organized, and any files left in place.
187
meirlabs