research-ideation
Quant-focused research ideation pipeline: scope selection (3 stages) → anchor-first literature grounding → single-core idea generation → iterative refinement → ELO tournament ranking (Final = N+R+C−D) → update evo-memory → user selects direction → expand into manuscript-quality proposal. Optimized for incremental, anchor-first contributions. Use when: user wants to find a quant research direction, brainstorm ideas within a scope stage, evaluate idea novelty, design a novel solution anchored to an existing paper, rank/compare research ideas, or generate a research proposal. Do NOT use for finding/searching/reading papers (use local-paper-navigator), literature survey reports (use research-survey), or planning a paper (use paper-planning).
CamusGIT · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add CamusGIT/EvoQuant --skill research-ideation技能说明
name: research-ideation description: "Quant-focused research ideation pipeline: scope selection (3 stages) → anchor-first literature grounding → single-core idea generation → iterative refinement → ELO tournament ranking (Final = N+R+C−D) → update evo-memory → user selects direction → expand into manuscript-quality proposal. Optimized for incremental, anchor-first contributions. Use when: user wants to find a quant research direction, brainstorm ideas within a scope stage, evaluate idea novelty, design a novel solution anchored to an existing paper, rank/compare research ideas, or generate a research proposal. Do NOT use for finding/searching/reading papers (use local-paper-navigator), literature survey reports (use research-survey), or planning a paper (use paper-planning)." allowed-tools: "write_file edit_file read_file think_tool execute" metadata: author: quant-research-team version: '3.0.0' tags: [core, research, ideation, tournament, proposal, quant, anchor-first, incremental]
Research Ideation
From research goal to ranked ideas and a detailed proposal.
Step 0: Load evo-memory (M_I)
↓
Step 1: Define Scope & Goal
↓
Step 2: Literature Grounding (MUST use local-paper-navigator scripts)
↓
Step 3: Generate Ideas (3 Anchor Papers × Innovator persona)
↓
Step 4: Refine Ideas (3 tracks × N iterations)
↓
Step 5: ELO Tournament → Present Top-3 to User
↓
Step 6: Update evo-memory (IDE)
↓
User Selects
↓
Step 7: Expand into Proposal
↓
Step 8: Validate and Iterate
When to Use
- User wants to find a research direction or brainstorm research ideas within a specific quant scope stage
- User wants to evaluate whether an idea is novel or worth pursuing
- User wants to rank or compare multiple research ideas
- User wants to generate a research proposal from an idea anchored to an existing paper
Note: This pipeline is optimized for quantitative research where incremental, anchor-first contributions are preferred over architectural redesigns.
When NOT to Use
- Finding/reading papers → use
local-paper-navigator - Literature survey report → use
research-survey - Planning a paper (story design, experiment plan) → use
paper-planning
Step 0: Load Prior Knowledge from evo-memory
Before any ideation begins, load Ideation Memory (M_I) from prior research cycles:
- Read M_I at
/memory/ideation-memory.md(refer toevo-memoryskill) - Select the top-2 entries (k_I=2) most relevant to the user's current goal by comparing each entry's Summary and Retrieval Tags against the goal
- Feasible directions from prior cycles → use as seeds in Step 3 (incorporate as candidate anchor directions alongside new ones, within the same scope stage)
- Unsuccessful directions marked as fundamental failures → use during idea pruning in Step 4 (prune any idea that matches a fundamental failure pattern)
- If M_I doesn't exist yet (first cycle), skip this step
This step prevents repeating known dead ends and builds on prior successes across research cycles.
Step 1: Define Research Scope & Goal
Research Scope
The long-term objective of this continual research program is to incrementally improve the quantitative research pipeline through publishable contributions in one of three core stages:
| Stage | Focus |
|---|---|
| Alpha Factor Research | Discover and validate economically meaningful alpha factors grounded in financial theory and empirical evidence |
| Alpha Generation Methodology | Develop more effective methods for discovering, generating, and evolving alpha factors automatically |
| Portfolio Strategy Research | Develop methods that transform one or multiple alpha signals into robust, diversified, and executable investment portfolios under realistic trading constraints. |
Each research session MUST focus on exactly one of the three stages above.
Hard constraints:
- The objective is not to redesign the entire pipeline, but to produce the smallest publishable improvement within a single stage.
- The proposed contribution should introduce one primary innovation, treating the remaining components as fixed background.
- Improvements should be incremental rather than architectural.
Research Goal
Within the chosen scope stage, define a concrete goal. Ask: "What is the smallest improvement that would be publishable in this stage?"
The goal should be narrow enough to complete in one research cycle, yet significant enough to advance the field.
Step 2: Literature Grounding (via local-paper-navigator)
Invoke local-paper-navigator to collect relevant papers from the local papers library. Do NOT skip this step or substitute with general knowledge — ideas must be grounded in real papers.
CRITICAL: All paper discovery in this step MUST use the local-paper-navigator skill and its scripts (local_search, xref_search, similar_papers, snippet_search, etc.). Using WebSearch, WebFetch, or any generic web search tool for finding papers is PROHIBITED. Generic web search returns blog posts, news articles, and low-quality results — only local-paper-navigator provides the local search, cross-reference, and keyword-similarity infrastructure needed for literature grounding.
Build Challenge-Insight Tree
From the collected papers, construct a challenge-insight tree — a many-to-many mapping between technical challenges and the insights/techniques that address them:
- Extract challenges: From each paper, what technical problem does it solve?
- Extract insights: What technique or key idea does it use?
- Map connections: Which insights address which challenges?
How this drives ideation:
- Challenges with few insights → unsolved problem (candidate for Step 3)
- Insights not yet applied to a challenge → cross-domain transfer opportunity (candidate for Step 4)
- Challenges with many insights → well-studied, avoid unless you hav