Back to Details

rw-review-methods

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

RW Review Methods

RW Review Methods

设计和执行可复现的系统综述、范围综述及其他证据综合流程。
Design and execute reproducible systematic reviews, scoping reviews, and other evidence synthesis processes.

启动

Startup

  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 round; if no materials are provided, only complete the parts allowed by the current evidence.
  3. Retrieve 
    references/atoms.jsonl
    when rule judgment is required; 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, and journal requirements may change, verify and record the date by opening the official links in 
    references/source-map.md
    .

工作阶段

Work Phases

  1. 确认综述目的、类型、研究问题、团队角色和注册要求。
  2. 预先定义纳排标准、信息来源、完整搜索式、日期范围和语言范围。
  3. 在正式检索前固定协议和检索策略，选择适用注册平台。范围综述使用 OSF，不送 PROSPERO。
  4. 核验不可变注册 ID、URL、带时区时间戳、协议版本和已注册文件哈希。注册门未通过时停止正式检索和题录导入。
  5. 建立去重、双人筛选、冲突处理和排除理由规则。
  6. 按研究类型确定提取字段、偏倚工具和结果层评价单位。
  7. 在看结果前写综合计划、异质性处理和敏感性分析。
  8. 报告协议偏离、筛选流程、研究特征、偏倚、综合结果和限制。
  1. Confirm the review purpose, type, research questions, team roles, and registration requirements.
  2. Predefine inclusion and exclusion criteria, information sources, complete search strategies, date ranges, and language ranges.
  3. Finalize the protocol and search strategy before formal retrieval, and select the applicable registration platform. Use OSF for scoping reviews; do not submit to PROSPERO.
  4. Verify immutable registration IDs, URLs, time-stamped with time zones, protocol versions, and hashes of registered files. Stop formal retrieval and reference import if registration requirements are not met.
  5. Establish rules for deduplication, dual-review screening, conflict resolution, and exclusion justifications.
  6. Determine extraction fields, bias assessment tools, and evaluation units for result layers based on study types.
  7. Write a synthesis plan, heterogeneity handling, and sensitivity analysis before examining results.
  8. Report protocol deviations, screening processes, study characteristics, biases, synthesized results, and limitations.

运行规则

Operational Rules

  • 先选综述类型，再选报告规范和方法手册。
  • PRISMA 是报告规范，不是完整的综述实施方法。
  • 范围综述用于描绘概念、证据类型和缺口，不默认回答效果大小。
  • 系统综述的纳排标准要在批量筛选前固定。
  • 正式证据综合必须在正式检索前完成适用的协议注册；范围综述使用 OSF。
  • 协议签字不等于协议注册。没有注册 ID、URL、时间戳和冻结文件证据时，不得放行检索。
  • 注册后的协议或检索策略发生变化时，停止并记录偏离；不得用新文件覆盖已注册版本。
  • 搜索日期、平台、完整搜索式和结果数量必须保留。
  • 双人筛选和冲突处理规则要在执行前确定。
  • 风险偏倚评价要与研究设计和具体结果匹配。
  • 研究质量、报告完整性和偏倚风险不能混成一个分数。
  • 是否进行统计合并由可比性和问题决定，不由研究数量决定。
  • 没有元分析时仍需预先定义叙述综合方法。
  • 协议偏离要记录时间、理由和对结论的影响。
  • 证据确定性评价要在结果层进行，并说明降级或升级理由。
  • Select the review type first, then choose the reporting guideline and methodology manual.
  • PRISMA is a reporting guideline, not a complete review implementation methodology.
  • Scoping reviews are used to map concepts, evidence types, and gaps; they do not default to answering effect sizes.
  • Inclusion and exclusion criteria for systematic reviews must be finalized before batch screening.
  • Formal evidence synthesis must complete applicable protocol registration before formal retrieval; use OSF for scoping reviews.
  • Protocol signing does not equal protocol registration. Do not proceed with retrieval without evidence of registration ID, URL, time-stamp, and frozen files.
  • If the registered protocol or search strategy changes, stop and record the deviation; do not overwrite the registered version with new files.
  • Search dates, platforms, complete search strategies, and result quantities must be retained.
  • Rules for dual-review screening and conflict resolution must be determined before execution.
  • Risk of bias assessment must match study design and specific results.
  • Study quality, reporting completeness, and risk of bias cannot be combined into a single score.
  • Whether to perform statistical pooling is determined by comparability and research questions, not by the number of studies.
  • A narrative synthesis method must be predefined even if no meta-analysis is conducted.
  • Record the time, reason, and impact on conclusions for protocol deviations.
  • Evidence certainty assessment must be conducted at the result layer, with justifications for downgrading or upgrading provided.

输出

Outputs

  • 协议、检索和执行清单。
  • 注册包和机器可读注册记录。
  • 筛选、提取、偏倚和综合模板。
  • 偏离记录、流程数据和报告检查表。
  • Protocol, retrieval, and execution checklists.
  • Registration packages and machine-readable registration records.
  • Templates for screening, extraction, bias assessment, and synthesis.
  • Deviation records, process data, and report checklists.

停止条件

Stop Conditions

  • 问题和纳排标准未定时，不开始批量筛选。
  • 要求注册的综述尚未完成注册时，不开始正式检索、导入或筛选。
  • 正式检索时间早于注册时间，或注册文件哈希不匹配时，停止并区分试检索与正式检索。
  • 不能只靠一个开放数据库声称检索完整。
  • 研究不可比较时，不因需要结论而强行合并。
  • 不把范围综述写成干预效果结论。
  • Do not start batch screening if the research question and inclusion/exclusion criteria are not defined.
  • Do not start formal retrieval, import, or screening if the review requiring registration has not completed registration.
  • Stop and distinguish between trial retrieval and formal retrieval if the formal retrieval time is earlier than the registration time, or if the registered file hash does not match.
  • Do not claim complete retrieval relying solely on one open database.
  • Do not force pooling of studies if they are not comparable, even if conclusions are needed.
  • Do not frame scoping reviews as conclusions on intervention effects.

独立运行

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 they exist; if installed alone, directly return instructions for the next step without stopping the current task.

来源纪律

Source Discipline

  • 把用户材料、公开来源、当前推断和未知事项分开。
  • 报告规范只检查报告透明度，不自动证明设计质量。
  • 公开来源摘要保存在 Skill 内；需要版本、费用、政策、API 或期刊现状时回到官方页面。
  • 不生成不存在的论文、数据、DOI、工具运行结果或期刊要求。
  • Skill、案例、测试和公开模板不得写入用户姓名、邮箱、机构、账号、令牌、绝对路径或私人项目内容。注册平台需要公开的作者信息由用户在平台中决定，不写入 Skill 源码。
  • Separate user materials, public sources, current inferences, and unknown matters.
  • Reporting guidelines only check report transparency and do not automatically prove design quality.
  • Public source abstracts are stored within the Skill; return to official pages when requiring versions, fees, policies, APIs, or current journal requirements.
  • Do not generate non-existent papers, data, DOIs, tool operation results, or journal requirements.
  • Do not write user names, emails, institutions, accounts, tokens, absolute paths, or private project content into Skill, cases, tests, or public templates. Author information requiring disclosure on registration platforms is determined by the user on the platform and not written into Skill source code.