scientify 1.2.1 → 1.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "scientify",
3
- "version": "1.2.1",
3
+ "version": "1.2.2",
4
4
  "description": "Scientify - AI-powered research workflow automation for OpenClaw. Includes idea generation, literature review, research pipeline skills, and arxiv tool.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: idea-generation
3
- description: "Generate innovative research ideas from a topic. SEARCHES arXiv/GitHub automatically, downloads papers, analyzes literature, outputs 5 novel ideas with citations. Use for: 找研究方向, 生成创新点, find research gaps, propose new methods. NOT for: summarizing papers (use /write-review-paper), literature survey (use /literature-survey)."
3
+ description: "Generate 5 innovative research ideas from collected papers. Analyzes literature, identifies gaps, proposes novel methods with citations. Use for: 找研究方向, 生成创新点, find research gaps. Requires papers in workspace (run /literature-survey first if needed)."
4
4
  metadata:
5
5
  {
6
6
  "openclaw":
@@ -13,389 +13,166 @@ metadata:
13
13
 
14
14
  # Idea Generation
15
15
 
16
- End-to-end workflow for generating innovative research ideas from a research topic. This skill implements a full research idea generation pipeline:
16
+ Generate innovative research ideas grounded in literature analysis. This skill reads existing papers, identifies research gaps, and produces 5 distinct ideas with citations.
17
17
 
18
- 1. Search papers and code repositories
19
- 2. Select and download references
20
- 3. Analyze literature and codebases
21
- 4. Generate multiple ideas
22
- 5. Select and enhance the best idea
23
- 6. Map to code implementations
18
+ **Core principle:** Ideas MUST be grounded in actual papers, not generated from model knowledge.
24
19
 
25
20
  ---
26
21
 
27
- ## ⚠️ CRITICAL: EXECUTION MODE
22
+ ## Step 1: Check Workspace Resources
28
23
 
29
- **AUTONOMOUS EXECUTION**: Execute ALL steps without asking for user confirmation at each step.
30
- - Do NOT ask "要我继续吗?" or "Should I proceed?"
31
- - You MAY spawn subagents for parallel tasks (e.g., downloading multiple papers)
32
- - Only ask user when there's a genuine ambiguity (e.g., which focus area to choose)
33
- - Checkpoints are for YOUR internal verification, not for asking user
24
+ First, check what resources already exist:
34
25
 
35
- **Run the entire workflow from Step 1 to Step 8 automatically.**
36
-
37
- ---
38
-
39
- ## ⚠️ CRITICAL: MANDATORY TOOL USAGE
40
-
41
- **DO NOT generate ideas from your own knowledge.** All ideas MUST be grounded in actual literature research.
42
-
43
- ### Blocking Requirements
44
-
45
- 1. **MUST call `arxiv` tool** to search papers - NO EXCEPTIONS
46
- 2. **MUST call `github_search` tool** to find repositories - NO EXCEPTIONS
47
- 3. **MUST write `search_results.md`** BEFORE proceeding to idea generation
48
- 4. **MUST reference specific papers** (with arXiv IDs) in generated ideas
49
- 5. **MUST clone actual repos** before code survey
50
-
51
- ### Anti-Pattern: DO NOT DO THIS
52
-
53
- ❌ User asks about "time series forecasting" → Agent immediately lists methods from memory
54
- ❌ Agent generates ideas without calling any search tools
55
- ❌ Agent skips to idea generation without `search_results.md` existing
56
-
57
- ### Correct Pattern: DO THIS
58
-
59
- ✅ User asks about "time series forecasting" → Agent calls `arxiv` tool with query
60
- ✅ Agent calls `github_search` tool to find implementations
61
- ✅ Agent writes search results to file
62
- ✅ Agent reads downloaded papers before generating ideas
63
- ✅ Ideas reference specific papers by arXiv ID
64
-
65
- ---
66
-
67
- ## Workspace Convention (Project-based)
26
+ ```bash
27
+ # Check active project
28
+ cat ~/.openclaw/workspace/projects/.active 2>/dev/null
68
29
 
69
- **IMPORTANT**: Each research topic uses its own project directory. Agent auto-selects or creates projects.
30
+ # Check papers
31
+ ls ~/.openclaw/workspace/projects/*/papers/ 2>/dev/null | head -20
70
32
 
71
- ```
72
- ~/.openclaw/workspace/
73
- └── projects/
74
- ├── .active # Current project ID (plain text file)
75
- ├── nlp-summarization/ # Project A
76
- │ ├── project.json # Project metadata
77
- │ ├── task.json # Research task definition
78
- │ ├── search_results.md # Search results
79
- │ ├── prepare_res.md # Selected repos summary
80
- │ ├── papers/ # Downloaded papers
81
- │ ├── repos/ # Cloned repositories
82
- │ └── ideas/ # Generated ideas
83
- ├── image-segmentation/ # Project B
84
- │ └── ...
85
- └── ...
33
+ # Check survey results
34
+ cat ~/.openclaw/workspace/projects/*/survey/clusters.json 2>/dev/null | head -5
86
35
  ```
87
36
 
88
- **All paths are project-relative**: `~/.openclaw/workspace/projects/{project_id}/`
37
+ ### Assess Available Resources
89
38
 
90
- **File existence = step completion.** Skip steps whose output already exists.
39
+ | Resource | Location | Status |
40
+ |----------|----------|--------|
41
+ | Papers | `$WORKSPACE/papers/` | Count: ? |
42
+ | Survey clusters | `$WORKSPACE/survey/clusters.json` | Exists: Y/N |
43
+ | Repos | `$WORKSPACE/repos/` | Count: ? |
91
44
 
92
45
  ---
93
46
 
94
- ## Step 0: Auto Project Management (REQUIRED)
47
+ ## Step 2: Ask User About Search Strategy
95
48
 
96
- **Autonomous - DO NOT ask user for confirmation.**
49
+ Based on workspace state, ask user:
97
50
 
98
- 1. Extract topic from user query → convert to kebab-case ID
99
- 2. Check `~/.openclaw/workspace/projects/` for existing match
100
- 3. Use existing or create new: `mkdir -p $PROJECT_ID/{papers,repos,ideas}`
101
- 4. Update `.active` file and set `$WORKSPACE` path
51
+ **If papers exist (≥5):**
52
+ > 📚 Found {N} papers in workspace from previous survey.
53
+ >
54
+ > Options:
55
+ > 1. **Use existing papers** - Generate ideas from current collection
56
+ > 2. **Search more** - Run `/literature-survey` to expand collection
57
+ > 3. **Quick search** - Add 5-10 more papers on specific topic
102
58
 
103
- > 📁 Using project: `{project_id}` (new/existing)
59
+ **If no papers:**
60
+ > 📭 No papers found in workspace.
61
+ >
62
+ > To generate grounded ideas, I need literature. Options:
63
+ > 1. **Run /literature-survey** - Comprehensive search (100+ papers, recommended)
64
+ > 2. **Quick search** - Fetch 10-15 papers on your topic now
65
+ > 3. **You provide papers** - Point me to existing PDFs/tex files
104
66
 
105
67
  ---
106
68
 
107
- ## Step 1: Parse Task
108
-
109
- Check `$WORKSPACE/task.json`. If missing, extract from user query:
69
+ ## Step 3: Acquire Resources (if needed)
110
70
 
111
- - **domain**: Research domain (e.g., "graph neural networks", "recommendation")
112
- - **focus** (optional): Specific problem or technique
113
- - **date_limit** (optional): Only consider papers before this date
71
+ ### Option A: Delegate to /literature-survey (Recommended)
114
72
 
115
- ```bash
116
- cat $WORKSPACE/task.json 2>/dev/null || echo "No task.json"
117
- ```
118
-
119
- Create task.json:
120
- ```json
121
- {
122
- "domain": "graph neural networks",
123
- "focus": "scalable transformers for node classification",
124
- "date_limit": "2024-01-01",
125
- "created": "2024-XX-XX"
126
- }
73
+ If user wants comprehensive search:
127
74
  ```
75
+ Please run: /literature-survey {topic}
128
76
 
129
- **Output:** `$WORKSPACE/task.json`
130
-
131
- ---
132
-
133
- ## Step 2: Search Papers and Code (MANDATORY)
134
-
135
- **⚠️ BLOCKING: You MUST complete this step before ANY idea generation.**
136
-
137
- ### 2.1 ArXiv Search (REQUIRED)
77
+ This will:
78
+ - Search 100+ papers systematically
79
+ - Filter by relevance (score ≥4)
80
+ - Cluster into research directions
81
+ - Save to $WORKSPACE/papers/
138
82
 
139
- **You MUST call the `arxiv` tool.** Example:
140
-
141
- ```
142
- Tool: arxiv
143
- Arguments:
144
- query: "text summarization transformer model"
145
- max_results: 10
146
- sort_by: "relevance"
147
- ```
148
-
149
- If `arxiv` tool is not available, use `WebSearch` with `site:arxiv.org`:
150
- ```
151
- Tool: WebSearch
152
- Arguments:
153
- query: "site:arxiv.org text summarization transformer model"
83
+ After survey completes, run /idea-generation again.
154
84
  ```
155
85
 
156
- ### 2.2 GitHub Search (REQUIRED)
157
-
158
- **You MUST call the `github_search` tool or search GitHub.** Example:
86
+ ### Option B: Quick Search (5-10 papers)
159
87
 
160
- ```
161
- Tool: github_search
162
- Arguments:
163
- query: "text summarization pytorch huggingface"
164
- sort: "stars"
165
- max_results: 20
166
- ```
88
+ For fast iteration, do minimal search:
167
89
 
168
- If `github_search` tool is not available, use `WebSearch`:
90
+ 1. **ArXiv search:**
169
91
  ```
170
- Tool: WebSearch
92
+ Tool: arxiv_search
171
93
  Arguments:
172
- query: "site:github.com text summarization pytorch stars:>100"
173
- ```
174
-
175
- ### 2.3 CHECKPOINT: Verify Search Completed
176
-
177
- Before proceeding, confirm:
178
- - [ ] Called arxiv/WebSearch for papers
179
- - [ ] Called github_search/WebSearch for repositories
180
- - [ ] Have at least 5 paper results
181
- - [ ] Have at least 5 repository results
182
-
183
- **If search returns 0 results, try different queries. DO NOT proceed without results.**
184
-
185
- ### 2.4 Compile Results
186
-
187
- Write to `$WORKSPACE/search_results.md`:
188
-
189
- ```markdown
190
- # Search Results
191
-
192
- ## Task
193
- - Domain: {domain}
194
- - Focus: {focus}
195
- - Date: {date}
196
-
197
- ## ArXiv Papers Found
198
-
199
- | # | Title | ArXiv ID | Year | Relevance |
200
- |---|-------|----------|------|-----------|
201
- | 1 | [Title](pdf_url) | 2401.xxxxx | 2024 | [Why relevant] |
202
- | 2 | ... | ... | ... | ... |
203
-
204
- ## GitHub Repositories Found
205
-
206
- | # | Repository | Stars | Language | Relevance |
207
- |---|------------|-------|----------|-----------|
208
- | 1 | [owner/repo](url) | 1.2k | Python | [Why relevant] |
209
- | 2 | ... | ... | ... | ... |
94
+ query: "{user_topic}"
95
+ max_results: 10
210
96
  ```
211
97
 
212
- **Output:** `$WORKSPACE/search_results.md`
213
-
214
- ---
215
-
216
- ## Step 3: Prepare - Select Repositories
217
-
218
- Read search results and select **at least 5** most valuable repositories.
219
-
220
- Selection criteria:
221
- - Direct implementation of relevant papers
222
- - High code quality (stars, documentation)
223
- - Active maintenance
224
- - Covers key techniques in the domain
225
-
226
- ### 3.1 Clone Selected Repos
227
-
98
+ 2. **Clone 3-5 reference repos:**
228
99
  ```bash
229
100
  mkdir -p $WORKSPACE/repos
230
- cd $WORKSPACE/repos
231
-
232
- # For each selected repo:
233
- git clone --depth 1 https://github.com/owner/repo1.git
234
- git clone --depth 1 https://github.com/owner/repo2.git
235
- # ... at least 5 repos
101
+ git clone --depth 1 {repo_url} $WORKSPACE/repos/{name}
236
102
  ```
237
103
 
238
- ### 3.2 Document Selection
239
-
240
- Write to `$WORKSPACE/prepare_res.md`:
241
-
242
- ```markdown
243
- # Selected Reference Codebases
244
-
245
- ## Selection Rationale
246
- [Why these repos were chosen]
247
-
248
- ## Repositories
249
-
250
- ### 1. repo1
251
- - **URL**: https://github.com/owner/repo1
252
- - **Paper**: [Associated paper if any]
253
- - **Key Components**:
254
- - `model/` - Model architecture
255
- - `train.py` - Training loop
256
- - **Usage**: [How this will help implement our idea]
257
-
258
- ### 2. repo2
259
- ...
260
-
261
- ## Reference Papers
262
- Based on these repos, the key papers to read are:
263
- 1. [Paper Title 1] - ArXiv: 2401.xxxxx
264
- 2. [Paper Title 2] - ArXiv: 2401.xxxxx
265
- ...
266
- ```
267
-
268
- **Output:** `$WORKSPACE/prepare_res.md` + `$WORKSPACE/repos/`
269
-
270
- ---
271
-
272
- ## Step 4: Download Papers
273
-
274
- For each paper referenced in prepare_res.md, download the source.
275
-
276
- **IMPORTANT: Download .tex source, NOT PDF.** .tex files are much easier for AI to read and extract information from.
277
-
278
- ### 4.1 Download .tex Source (RECOMMENDED - Use arxiv tool)
279
-
280
- Use the `arxiv` tool with `download: true` to automatically download and extract .tex sources:
281
-
282
- ```
283
- Tool: arxiv
284
- Arguments:
285
- query: "abstractive summarization long document"
286
- max_results: 10
287
- download: true
288
- output_dir: "$WORKSPACE/papers"
289
- ```
290
-
291
- The tool will:
292
- 1. Search for papers matching your query
293
- 2. Download .tex source from `https://arxiv.org/src/{arxiv_id}`
294
- 3. Extract tar.gz archives automatically
295
- 4. Fall back to PDF if .tex is unavailable
296
- 5. Return a `downloads` array showing what was downloaded
297
-
298
- **Output format:**
299
- ```json
300
- {
301
- "papers": [...],
302
- "downloads": [
303
- {"arxiv_id": "2404.04429", "format": "tex", "files": ["main.tex", "methods.tex"]},
304
- {"arxiv_id": "2308.03664", "format": "pdf", "files": ["2308.03664.pdf"], "error": "tex unavailable"}
305
- ],
306
- "output_dir": "$WORKSPACE/papers"
307
- }
308
- ```
309
-
310
- ### 4.2 Manual Download (Fallback)
311
-
312
- If the arxiv tool is unavailable, use bash:
104
+ 3. **Download paper sources:**
313
105
  ```bash
314
106
  mkdir -p $WORKSPACE/papers/{arxiv_id}
315
- cd $WORKSPACE/papers/{arxiv_id}
316
- curl -L "https://arxiv.org/src/{arxiv_id}" -o source.tar.gz
317
- tar -xzf source.tar.gz 2>/dev/null || mv source.tar.gz main.tex
107
+ curl -L "https://arxiv.org/src/{arxiv_id}" | tar -xz -C $WORKSPACE/papers/{arxiv_id}
318
108
  ```
319
109
 
320
- ### 4.3 Document Downloads
321
-
322
- Write to `$WORKSPACE/papers/download_log.md`:
323
-
324
- ```markdown
325
- # Downloaded Papers
326
-
327
- | ArXiv ID | Title | Format | Status |
328
- |----------|-------|--------|--------|
329
- | 2404.04429 | Physics-Informed ML for Battery... | .tex | ✓ |
330
- | 2308.03664 | Two-stage Early Prediction... | .tex | ✓ |
331
- | 2401.99999 | Some Other Paper | .pdf | ✓ (tex unavailable) |
332
- ```
333
-
334
- **Output:** `$WORKSPACE/papers/`
335
-
336
110
  ---
337
111
 
338
- ## Step 5: Generate Ideas (5 Ideas)
112
+ ## Step 4: Analyze Literature
339
113
 
340
- **⚠️ BLOCKING: DO NOT start this step unless Steps 2-4 are complete.**
114
+ **Prerequisites:** At least 5 papers in `$WORKSPACE/papers/`
341
115
 
342
- ### Pre-requisite Checkpoint
116
+ ### 4.1 Read Papers
343
117
 
344
- Before generating ANY ideas, verify these files exist:
345
- - [ ] `$WORKSPACE/search_results.md` - search results from Step 2
346
- - [ ] `$WORKSPACE/prepare_res.md` - selected repos from Step 3
347
- - [ ] At least 3 papers downloaded in `$WORKSPACE/papers/`
118
+ For each paper, extract:
119
+ - Core contribution (1 sentence)
120
+ - Key method/formula
121
+ - Limitations mentioned
122
+ - Future work suggestions
348
123
 
349
- **If any file is missing, GO BACK and complete the previous steps.**
124
+ **Long papers (>50KB):** See `references/reading-long-papers.md`
350
125
 
351
- This is the core intellectual step. Generate **exactly 5 distinct innovative ideas**.
352
-
353
- **IMPORTANT: Ideas must be grounded in the literature you just read. Each idea MUST:**
354
- - Reference at least 2 specific papers by arXiv ID
355
- - Identify specific limitations from those papers
356
- - Propose improvements based on gaps found in the literature
357
-
358
- ### 5.1 Analyze Literature First (REQUIRED)
359
-
360
- For each paper in `papers/`:
361
- 1. Read thoroughly (especially: abstract, method, experiments, limitations)
362
- 2. Extract: core contribution, math formulas, limitations, future work
363
- 3. Note connections to other papers
364
-
365
- **Long Papers (>50KB):** See `references/reading-long-papers.md` for chunked reading strategy.
366
-
367
- For each repo in `repos/`:
368
- 1. Understand structure: `gen_code_tree_structure` equivalent
369
- 2. Identify key implementations
370
- 3. Note reusable components
371
-
372
- ### 5.2 Identify Research Gaps
126
+ ### 4.2 Identify Research Gaps
373
127
 
374
128
  Look for:
375
129
  - Common limitations across papers
376
- - Unexplored combinations of techniques
130
+ - Unexplored technique combinations
377
131
  - Scalability issues
378
132
  - Assumptions that could be relaxed
379
133
 
380
- ### 5.3 Generate 5 Ideas
134
+ Document gaps in `$WORKSPACE/ideas/gaps.md`:
135
+ ```markdown
136
+ # Research Gaps Identified
137
+
138
+ ## Gap 1: [Description]
139
+ - Mentioned in: [paper1], [paper2]
140
+ - Why important: ...
141
+
142
+ ## Gap 2: [Description]
143
+ ...
144
+ ```
145
+
146
+ ---
147
+
148
+ ## Step 5: Generate 5 Ideas
381
149
 
382
150
  Create `$WORKSPACE/ideas/idea_1.md` through `idea_5.md` using template in `references/idea-template.md`.
383
151
 
384
- **Key requirements:**
385
- - Each idea must cite ≥2 papers by arXiv ID
386
- - Use different strategies (see template): combination, simplification, generalization, constraint relaxation, architecture innovation
152
+ **Requirements:**
153
+ - Each idea cites ≥2 papers by arXiv ID
154
+ - Use different strategies:
387
155
 
388
- **❌ REJECTED if:** No arXiv IDs cited, or ideas not grounded in literature
156
+ | Idea | Strategy |
157
+ |------|----------|
158
+ | 1 | Combination - merge 2+ techniques |
159
+ | 2 | Simplification - reduce complexity |
160
+ | 3 | Generalization - extend to new domain |
161
+ | 4 | Constraint relaxation - remove assumption |
162
+ | 5 | Architecture innovation - new design |
389
163
 
390
- **Output:** `$WORKSPACE/ideas/idea_1.md` through `idea_5.md`
164
+ **❌ REJECTED if:** No arXiv IDs cited, or ideas not grounded in literature
391
165
 
392
166
  ---
393
167
 
394
168
  ## Step 6: Select and Enhance Best Idea
395
169
 
396
- ### 6.1 Evaluate All Ideas
170
+ ### 6.1 Score All Ideas
397
171
 
398
- Score each idea on Novelty/Feasibility/Impact (1-5). Select highest total.
172
+ | Idea | Novelty | Feasibility | Impact | Total |
173
+ |------|---------|-------------|--------|-------|
174
+ | 1 | /5 | /5 | /5 | /15 |
175
+ | ... | | | | |
399
176
 
400
177
  ### 6.2 Enhance Selected Idea
401
178
 
@@ -404,62 +181,25 @@ Create `$WORKSPACE/ideas/selected_idea.md` with:
404
181
  - Architecture choices
405
182
  - Hyperparameters
406
183
  - Implementation roadmap
407
- - Failure modes & mitigations
408
-
409
- **Output:** `$WORKSPACE/ideas/selected_idea.md`
410
184
 
411
185
  ---
412
186
 
413
- ## Step 7: Code Survey - Map Idea to Implementations
187
+ ## Step 7: Code Survey
414
188
 
415
- Map each **atomic concept** in the selected idea to code in reference repos.
189
+ Map idea concepts to reference implementations.
416
190
 
417
- See `references/code-mapping.md` for detailed template.
418
-
419
- **Quick steps:**
420
- 1. Extract atomic concepts from `selected_idea.md`
421
- 2. Search repos: `grep -r "class.*Attention" $WORKSPACE/repos/`
422
- 3. Document mapping to `$WORKSPACE/ideas/implementation_report.md`
191
+ See `references/code-mapping.md` for template.
423
192
 
424
193
  **Output:** `$WORKSPACE/ideas/implementation_report.md`
425
194
 
426
195
  ---
427
196
 
428
- ## Step 8: Final Summary
197
+ ## Step 8: Summary
429
198
 
430
- Create `$WORKSPACE/ideas/summary.md` with:
431
- - Task overview (domain, focus)
432
- - Resources gathered (papers, repos count)
199
+ Create `$WORKSPACE/ideas/summary.md`:
433
200
  - All 5 ideas with scores
434
201
  - Selected idea details
435
- - Next steps: `/research-pipeline` or manual implementation
436
-
437
- **Output:** `$WORKSPACE/ideas/summary.md`
438
-
439
- ---
440
-
441
- ## Quality Checklist
442
-
443
- Before completing, verify:
444
-
445
- - [ ] At least 5 repos cloned in `repos/`
446
- - [ ] At least 3 papers downloaded in `papers/`
447
- - [ ] All 5 ideas are substantially different
448
- - [ ] Selected idea has complete math formulations
449
- - [ ] Implementation report covers ALL atomic concepts
450
- - [ ] Each concept has actual code reference (not placeholder)
451
- - [ ] Evaluation plan has specific datasets and metrics
452
-
453
- ---
454
-
455
- ## Integration with Other Skills
456
-
457
- **After idea-generation:**
458
- - `/research-pipeline` → Implement the selected idea
459
-
460
- **To gather more resources:**
461
- - `/literature-survey` → Comprehensive paper collection
462
- - `/write-review-paper` → Synthesize into review
202
+ - Next steps: `/research-pipeline` to implement
463
203
 
464
204
  ---
465
205
 
@@ -467,19 +207,15 @@ Before completing, verify:
467
207
 
468
208
  | User Says | Action |
469
209
  |-----------|--------|
470
- | "Generate research ideas for NLP" | Full workflow (Steps 1-8) |
471
- | "Search papers on X" | Steps 1-2 only |
472
- | "I have papers, generate ideas" | Skip to Step 5 |
473
- | "Enhance this idea: ..." | Skip to Step 6-7 |
474
- | "Map this idea to code" | Step 7 only |
210
+ | "Generate ideas for X" | Check workspace ask strategy → generate |
211
+ | "I have papers, generate ideas" | Skip to Step 4 |
212
+ | "Enhance idea N" | Jump to Step 6 |
213
+ | "Map to code" | Jump to Step 7 |
475
214
 
476
215
  ---
477
216
 
478
- ## Batch Processing Rule
479
-
480
- If more than 10 papers/repos to analyze:
481
- 1. First pass: Quick scan all (abstract/README only)
482
- 2. Select top 5-7 for deep analysis
483
- 3. Generate ideas from deep analysis
217
+ ## Integration
484
218
 
485
- Do NOT process all resources with full detail - context will overflow.
219
+ - **Before:** `/literature-survey` to collect papers
220
+ - **After:** `/research-pipeline` to implement selected idea
221
+ - **Alternative:** `/write-review-paper` to write survey instead