研究构思
- 作者仓库星标 1,203
- 作者仓库 claude-code-my-workflow
- 领域
- 数据
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @pedrohcgs · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Research Ideation
Generate structured research questions, testable hypotheses, and empirical strategies from a topic, phenomenon, or dataset.
**Input:** `$ARGUMENTS` — a topic (e.g., "minimum wage effects on employment"), a phenomenon (e.g., "why do firms cluster geographically?"), or a dataset description (e.g., "panel of US counties with pollution and health outcomes, 2000-2020").
---
## Steps
1. **Understand the input.** Read `$ARGUMENTS` and any referenced files. Check `master_supporting_docs/` for related papers. Check `.claude/rules/` for domain conventions.
2. **Generate 3-5 research questions** ordered from descriptive to causal:
- **Descriptive:** What are the patterns? (e.g., "How has X evolved over time?")
- **Correlational:** What factors are associated? (e.g., "Is X correlated with Y after controlling for Z?")
- **Causal:** What is the effect? (e.g., "What is the causal effect of X on Y?")
- **Mechanism:** Why does the effect exist? (e.g., "Through what channel does X affect Y?")
- **Policy:** What are the implications? (e.g., "Would policy X improve outcome Y?")
3. **Tag each RQ with a likely paper type** (drawn from `methods-referee.md`):
- `reduced-form` (DiD, IV, RD, event study, synthetic control)
- `structural` (estimation of a fully-specified model)
- `theory+empirics` (formal model + empirical test of its predictions)
- `descriptive` (measurement, data construction, pattern documentation)
- `formal-theory` (pure theory, no empirical test in this paper)
- `survey-experiment` (vignette, conjoint, list-experiment)
- `unsure` (when multiple types are plausible — the user can pick later via `/interview-me`)
Use `.claude/references/discipline-cards.md` to bias the distribution by field (econ vs poli-sci default frequencies differ — e.g., poli-sci skews more toward `survey-experiment` and `formal-theory` than econ does).
4. **For each research question, develop:**
- **Hypothesis:** A testable prediction with expected sign/magnitude
- **Identification strategy:** How to establish causality (DiD, IV, RDD, synthetic control, etc.)
- **Data requirements:** What data would be needed? Is it available?
- **Key assumptions:** What must hold for the strategy to be valid?
- **Potential pitfalls:** Common threats to identification
- **Related literature:** 2-3 papers using similar approaches
5. **Rank the questions** by feasibility and contribution.
6. **Save the output** to `quality_reports/research_ideation_[sanitized_topic].md`
---
## Output Format
```markdown
# Research Ideation: [Topic]
**Date:** [YYYY-MM-DD]
**Input:** [Original input]
## Overview
[1-2 paragraphs situating the topic and why it matters]
## Research Questions
### RQ1: [Question] (Feasibility: High/Medium/Low)
**Type:** Descriptive / Correlational / Causal / Mechanism / Policy
**Paper type:** reduced-form / structural / theory+empirics / descriptive / formal-theory / survey-experiment / unsure
**Hypothesis:** [Testable prediction]
**Identification Strategy:**
- **Method:** [e.g., Difference-in-Differences]
- **Treatment:** [What varies and when]
- **Control group:** [Comparison units]
- **Key assumption:** [e.g., Parallel trends]
**Data Requirements:**
- [Dataset 1 — what it provides]
- [Dataset 2 — what it provides]
**Potential Pitfalls:**
1. [Threat 1 and possible mitigation]
2. [Threat 2 and possible mitigation]
**Related Work:** [Author (Year)], [Author (Year)]
---
[Repeat for RQ2-RQ5]
## Ranking
| RQ | Feasibility | Contribution | Priority |
|----|-------------|-------------|----------|
| 1 | High | Medium | ... |
| 2 | Medium | High | ... |
## Suggested Next Steps
1. [Most promising direction and immediate action]
2. [Data to obtain]
3. [Literature to review deeper]
```
---
## Post-Flight Verification (mandatory, CoVe)
Before returning the ideation report, run the Post-Flight Verification protocol from [`.claude/rules/post-flight-verification.md`](../../rules/post-flight-verification.md). Research ideation is hallucination-prone in three specific ways:
1. **Negative-literature claims** — "no prior work studies X" is frequently wrong.
2. **Dataset structure claims** — "The CPS contains field `educ_attain`" can be confidently wrong about variable names, coverage years, or restricted-access status.
3. **Estimator feasibility claims** — "this works with panel fixed effects" can misstate an identification assumption.
### Steps
1. **Extract claims** from the draft ideation report: each negative-literature claim, each named dataset with attributed fields, each claimed identification strategy + required data structure.
2. **Generate verification questions** per claim. Example: "Has Card & Krueger, Autor, or anyone in the last 10 years studied X? Search Google Scholar + NBER working papers." / "Does IPUMS-CPS include the `educ_attain` variable 1990–2024?"
3. **Spawn `claim-verifier`** via `Task` with `subagent_type=claim-verifier` and `context=fork`. Hand it claims + questions + source pointers (WebSearch allowed, NBER/SSRN URLs preferred, dataset codebooks preferred). Do NOT include the draft.
4. **Reconcile:** PASS → attach green block; PARTIAL → mark uncertain RQs with flags; FAIL → rewrite the affected RQ/hypothesis/strategy.
### Skip conditions
- `--no-verify` flag
- User explicitly says "I'll verify the literature myself"
---
## Principles
- **Be creative but grounded.** Push beyond obvious questions, but every suggestion must be empirically feasible.
- **Think like a referee.** For each causal question, immediately identify the identification challenge.
- **Consider data availability.** A brilliant question with no available data is not actionable.
- **Suggest specific datasets** where possible (FRED, Census, PSID, administrative data, etc.).
章节与文件索引
按说明文件中的顺序排列。
步骤
飞行后验证(强制,Cove)
跳过条件
原则
文件/命令 -> $ARGUMENTS · master_supporting_docs/ · .claude/rules/ · methods-referee.md · reduced-form · structural · theory+empirics · descriptive
内容校验值 -> a369b0438bbc
当前原文的自动摘译,尚未人工审校。
步骤
了解输入。阅读
$ARGUMENTS和任何引用的文件。检查master_supporting_docs/相关论文。检查.claude/rules/的域约定。生成 3-5 个研究问题,按从描述性到因果性的顺序排列: 描述性:有哪些模式? (例如,“X 随着时间的推移如何演变?”)相关性:哪些因素相关? (例如,“控制 Z 后 X 与 Y 相关吗?”)飞行后验证(强制,Cove)
在返回构思报告之前,请从
.claude/rules/post-flight-verification.md运行飞行后验证协议。研究理念在三个具体方面容易产生幻觉: 负面文献主张——“没有先前的工作研究 X”经常是错误的。数据集结构声明——“CPS 包含字段educ_attain”在变量名称、覆盖年份或限制访问状态方面可能是错误的。跳过条件
--no-verify标记用户明确表示“我会亲自验证文献”原则
要有创意,但要脚踏实地。超越显而易见的问题,但每项建议都必须在经验上可行。像裁判一样思考。对于每个因果问题,立即确定识别挑战。考虑数据可用性。没有可用数据的精彩问题是不可行的。尽可能建议具体的数据集(FRED、人口普查、PSID、管理数据等)。