科研 Skill

综述模块拆解规划

decompose-review-modules

Breaks a refined literature-review question into 3-5 non-overlapping modules to build a reading map, outline, or search plan. Use when structuring a literature review.

发布者 Codar安全审核通过v0.1.0更新于 2026-11-18

SKILL.md

Decompose Review Modules

Discipline And Interview Setup

Read discipline-routing.md, then only the selected discipline profile. Reuse the user's existing brief; do not restart intake at each stage. For journalism/communication or information science, use that profile's concepts, extraction fields, and appraisal checks instead of a generic social-science template.

When the user requests "grill me", 追问, or 模拟答辩, read research-interview.md. Ask one decision-relevant question per turn and wait; do not generate the stage deliverable until enough decisions are settled or the user asks to proceed. In quick/no-question mode, record assumptions and continue without inventing answers.

For evidence extraction or drafting, read review-workflow.md. With no sources, give a plan or outline, not a purported synthesis. If reference files are unavailable, retain the source guardrails below and state that discipline guidance is missing.

Goal

Convert one core research question into a small set of review modules that cover the key dimensions of the problem without collapsing into a loose topic list.

Workflow

  1. Restate the core question in one sentence.
  2. Identify the main actors, mechanisms, outcomes, contexts, and constraints embedded in the question.
  3. Propose 3-5 modules that are independent enough to become review sections.
  4. Check whether sub-questions repeat. A paper may inform several modules; record separate evidence contributions rather than forcing each paper into one bucket.
  5. Check coverage: the modules together should explain the main question's key dimensions.
  6. Assess coverage only from the supplied or retrieved corpus. Without it, label module coverage "not assessed"; do not infer a gap or literature density from the outline.

Module Design Rules

Good modules should be:

  • Mutually distinguishable: each module asks a different sub-question.
  • Collectively useful: together they help answer the core question.
  • Literature-searchable: each can generate keywords, inclusion criteria, and section titles.
  • Analytical rather than decorative: use a distinct synthesis task for each section, including conceptual or historical tasks; a mechanism is not mandatory.

Common Module Axes

Choose axes that fit the question:

  • Drivers: economic incentives, capability thresholds, social networks, institutional environment.
  • Mechanisms: perception, decision process, resource allocation, coordination, feedback loops.
  • Actors: individuals, organizations, platforms, governments, communities.
  • Stages: adoption, use, persistence, exit, diffusion.
  • Contexts: region, industry, policy period, population type, technology maturity.
  • Outcomes: performance, equity, participation, sustainability, resilience.

Output Format

Provide:

## Core Question

[One sentence]

## Proposed Modules

| Module | Sub-question | Include | Exclude |
|---|---|---|---|
| ... | ... | ... | ... |

## Coverage Check

- What the modules cover well: ...
- Possible missing dimension: ...
- Possible overlap to revise: ...

## Suggested Review Outline

1. ...
2. ...
3. ...

## 待核实清单

[Unverified sources, "未查到" results, sentences marked [需补来源], and inferences that still need checking; write "无" if empty]

## 给作者的问题

[Judgment calls that belong to the author; write "无" if empty]

The output sections above, and the two closing sections, keep fixed names and order; see references/output-contract.md (a copy bundled in this skill folder).

Guardrails

  • Do not create more than five main modules unless the user explicitly asks for a large taxonomy.
  • Do not organize modules only by author, year, country, or method unless that is the analytical point.
  • When the user gives only a broad topic, first invoke question refinement logic before decomposing modules.
  • Source integrity: follow references/source-integrity.md. Search keywords and expected literature distribution are suggestions, not findings; do not name specific papers unless the user provided them. Use only sources the user provided or that are verified, tag each with a status (用户提供 / 已核验 / 未核验), write "未查到" instead of completing authors, year, journal, or pages, and put anything unverified in ## 待核实清单. If that file is not available, still apply these rules.

示例提示词

帮我把这个综述问题拆成几个不重叠的模块,规划阅读与写作框架。

所属插件

跨学科科研方法跨学科通用科研方法:系统综述与元分析、预注册、实验与问卷设计、文献矛盾与研究空白、科学计量与专利分析、可复现研究、答辩与审稿回复。

安装该插件会一并获得同领域的 54 个 Skill / MCP。

同插件的其他科研 Skill

常见问题

综述模块拆解规划能做什么?

Breaks a refined literature-review question into 3-5 non-overlapping modules to build a reading map, outline, or search plan. Use when structuring a literature review。

如何安装综述模块拆解规划?

在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「综述模块拆解规划」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。

综述模块拆解规划需要哪些权限?

该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。

综述模块拆解规划经过官方审核吗?

是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。