Back to Details

rw-research-question

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

RW Research Question

RW Research Question

把研究兴趣转成可界定、可检索、可证伪和可执行的问题。
Transform research interests into definable, searchable, falsifiable, and executable research questions.

启动

Activation

  1. 读取 
    references/standalone.md
    、
    references/method.md
    和 
    references/standards.md
    。
  2. 读取用户本轮提供的材料；没有材料时，只完成当前证据允许的部分。
  3. 需要规则判断时检索 
    references/atoms.jsonl
    ；遇到相似任务时读取 
    references/cases.md
    。
  4. 需要选择方法或工具时读取 
    references/domain-guide.md
    ，并使用 
    assets/worksheet.md
    组织交付。
  5. 读取 
    references/acceptance.md
    。
    references/behavior-tests.json
    只用于测试，不作为用户任务事实。
  6. 当前文献、API、报告规范和期刊要求可能变化时，打开 
    references/source-map.md
    中的官方链接核验并记录日期。
  1. Read 
    references/standalone.md
    , 
    references/method.md
    , and 
    references/standards.md
    .
  2. Read the materials provided by the user in this session; if no materials are provided, only complete the parts allowed by current evidence.
  3. Retrieve 
    references/atoms.jsonl
    when rule judgment is needed; read 
    references/cases.md
    when encountering similar tasks.
  4. Read 
    references/domain-guide.md
    when selecting methods or tools, and use 
    assets/worksheet.md
    to organize deliverables.
  5. Read 
    references/acceptance.md
    . 
    references/behavior-tests.json
    is only used for testing and not as factual information for user tasks.
  6. When current literature, APIs, report specifications, or journal requirements may change, verify by opening the official links in 
    references/source-map.md
    and record the date.

工作阶段

Work Phases

  1. 保留原始兴趣、决策场景和用户真正想解释的现象。
  2. 识别问题类型：描述、关联、因果、诊断、预测、体验、实施、经济或证据综合。
  3. 定义人群或情境、现象或干预、比较、结果、时间和研究层级。
  4. 为核心构念写操作性定义、可观察指标和不可接受的替代定义。
  5. 列出至少两个替代解释、一个反例和会改变结论的结果。
  6. 输出主问题、子问题、检索概念、数据要求和不可回答部分。
  1. Retain the original interest, decision-making scenario, and the phenomenon the user actually wants to explain.
  2. Identify the problem type: descriptive, correlational, causal, diagnostic, predictive, experiential, implementation, economic, or evidence synthesis.
  3. Define the population or context, phenomenon or intervention, comparison, outcome, time, and research level.
  4. Write operational definitions, observable indicators, and unacceptable alternative definitions for core constructs.
  5. List at least two alternative explanations, one counterexample, and outcomes that would change the conclusion.
  6. Output the main question, sub-questions, search concepts, data requirements, and unanswerable parts.

运行规则

Operational Rules

  • 先选择问题类型，再选择问题框架；PICO 不是所有问题的默认格式。
  • 可检索的问题要把核心构念拆成概念和同义词。
  • 可执行的问题要说明能够取得什么数据，而不是只写理想数据。
  • 可证伪的问题要说明何种观察会削弱主要解释。
  • 构念定义不清时，样本量和统计方法都不能补救。
  • 数据已经存在，只能限制问题，不能自动证明问题有价值。
  • 描述问题不能在输出中变成因果问题。
  • 预测问题要区分模型开发、内部验证、外部验证和临床效用。
  • 定性问题要说明经验、过程或意义所处的情境。
  • 实施问题要区分干预效果和实施结果。
  • 研究问题必须有范围边界，不能靠无限加变量解决。
  • 最终问题应能生成检索式、纳排标准或研究设计入口。
  • Select the problem type first, then the problem framework; PICO is not the default format for all questions.
  • For searchable questions, split core constructs into concepts and synonyms.
  • For executable questions, specify what data can be obtained, rather than just writing ideal data.
  • For falsifiable questions, specify what observations would weaken the main explanation.
  • Unclear construct definitions cannot be remedied by sample size or statistical methods.
  • If data already exists, only limit the question; do not automatically prove the question is valuable.
  • Descriptive questions cannot be turned into causal questions in the output.
  • For predictive questions, distinguish between model development, internal validation, external validation, and clinical utility.
  • For qualitative questions, specify the context in which experience, process, or meaning occurs.
  • For implementation questions, distinguish between intervention effects and implementation outcomes.
  • Research questions must have scope boundaries; do not solve problems by adding unlimited variables.
  • The final question should be able to generate search strategies, inclusion-exclusion criteria, or entry points for research design.

输出

Output

  • 主研究问题和子问题。
  • 构念、边界、替代解释和证伪条件。
  • 检索概念、数据要求和下一步。
  • Main research question and sub-questions.
  • Constructs, boundaries, alternative explanations, and falsification conditions.
  • Search concepts, data requirements, and next steps.

停止条件

Termination Conditions

  • 核心构念无法定义时，停止在构念澄清。
  • 没有可取得的数据或可接触的研究对象时，标记不可执行。
  • 不因新颖措辞声称研究存在文献缺口。
  • 不把相关性问题改写成因果结论。
  • Stop at construct clarification when core constructs cannot be defined.
  • Mark as non-executable when there is no accessible data or research subjects.
  • Do not claim a literature gap based on novel wording.
  • Do not rewrite correlational questions into causal conclusions.

独立运行

Standalone Operation

  • 默认不读取私人工作区、个人语料目录或预设 research-lab。
  • 用户提供的文件、文本、链接和数据是当前任务输入，不是安装依赖。
  • 网络不可用时，使用 Skill 内的稳定方法继续；需要当前事实的部分标记为待核验。
  • 本包内其他科研 Skill 存在时可以接续；单独安装时直接返回下一步说明，不停止当前任务。
  • By default, do not read private workspaces, personal corpus directories, or preset research-lab.
  • Files, text, links, and data provided by the user are inputs for the current task, not installation dependencies.
  • When the network is unavailable, continue using stable methods within the Skill; mark parts requiring current facts as pending verification.
  • Can connect with other research Skills in this package if available; when installed alone, directly return instructions for next steps without stopping the current task.

来源纪律

Source Discipline

  • 把用户材料、公开来源、当前推断和未知事项分开。
  • 报告规范只检查报告透明度，不自动证明设计质量。
  • 公开来源摘要保存在 Skill 内；需要版本、费用、政策、API 或期刊现状时回到官方页面。
  • 不生成不存在的论文、数据、DOI、工具运行结果或期刊要求。
  • Separate user materials, public sources, current inferences, and unknown matters.
  • Report specifications only check report transparency; do not automatically prove design quality.
  • Public source abstracts are stored within the Skill; return to official pages when needing version, cost, policy, API, or journal status.
  • Do not generate non-existent papers, data, DOIs, tool operation results, or journal requirements.