科研 Skill
研究选题构思设计
brainstorming-research
Explores research intent, field state, methodology, and ethics, then writes an approved design doc. Use before starting a new research question or chapter.
SKILL.md
Brainstorming Research Ideas Into Designs
Turn a vague research interest into a written, approvable design doc. Act as an ideation partner, not an instructor. Probe, challenge, surface unexamined assumptions — then lock the design down on paper so later phases have something stable to build on.
If unmet: explain to the user what's missing, ask for a short reason for
skipping (e.g. "mini-review, not a standalone project"), write it to
knowledge/_meta/gate-overrides.log, and continue. Repeated skipping is a
signal that the routine is fraying — the lint stats make that visible.
Anti-Pattern: "This Is Too Simple To Need A Design"
Every research project goes through this process. A single-source review, a short methodological note, a conference abstract — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a half page for truly simple projects), but you MUST present it and get approval.
Checklist
Create a task-list item for each. Complete in order:
- Explore project context — read existing
input/ideas/*,input/description/*, recentknowledge/_meta/log.md, check git for parallel work - Ask clarifying questions — one at a time — what is the research question, what has been seen already, what would success look like. The user formulates the question first, in their own words, however rough; you sharpen it afterwards (see Phase 1)
- Ask for the AI-use rules — which institution / publisher / journal / funder will receive the output, and what do their rules say about AI tools (allowed uses, required disclosure form)? Unknown is a valid answer — record it as an open point. This goes into the design doc's
AI-Use Rulessection and is read again byfinishing-a-research-project - Assess scope — is this a single focused inquiry or an umbrella of independent sub-projects? If the latter, decompose first (each sub-project gets its own design doc)
- Propose 2–3 approaches — with trade-offs and your recommendation, grounded in disciplinary norms
- Surface hidden constraints — ethics (ancient human remains, epigraphic access permissions), data rights, linguistic reach, time horizon, collaborator availability
- Present design in sections — get user approval after each: question, state of the field (short), method, data, output target, risks
- Write design doc — save to
input/ideas/<slug>-design.mdusing the template below - Design self-review — scan for placeholders, contradictions, scope creep, ambiguous claims; fix inline
- User reviews the written doc — ask for sign-off on the file before handing off
- Transition to writing-research-plan — once approved, invoke that skill. Do NOT invoke anything else.
Process Flow
digraph brainstorming_research {
"Explore project context" [shape=box];
"Scope: single or umbrella?" [shape=diamond];
"Decompose into sub-projects" [shape=box];
"Ask clarifying questions" [shape=box];
"Propose 2-3 approaches" [shape=box];
"Surface hidden constraints" [shape=box];
"Present design sections" [shape=box];
"User approves each section?" [shape=diamond];
"Write design doc" [shape=box];
"Self-review (fix inline)" [shape=box];
"User approves written doc?" [shape=diamond];
"Invoke writing-research-plan" [shape=doublecircle];
"Explore project context" -> "Scope: single or umbrella?";
"Scope: single or umbrella?" -> "Decompose into sub-projects" [label="umbrella"];
"Scope: single or umbrella?" -> "Ask clarifying questions" [label="single"];
"Decompose into sub-projects" -> "Ask clarifying questions";
"Ask clarifying questions" -> "Propose 2-3 approaches";
"Propose 2-3 approaches" -> "Surface hidden constraints";
"Surface hidden constraints" -> "Present design sections";
"Present design sections" -> "User approves each section?";
"User approves each section?" -> "Present design sections" [label="no, revise"];
"User approves each section?" -> "Write design doc" [label="yes"];
"Write design doc" -> "Self-review (fix inline)";
"Self-review (fix inline)" -> "User approves written doc?";
"User approves written doc?" -> "Write design doc" [label="changes requested"];
"User approves written doc?" -> "Invoke writing-research-plan" [label="approved"];
}
Terminal state: invoke writing-research-plan. Do NOT invoke literature-review, ingest-source, or any execution skill directly — those belong after the plan is written.
Design Doc Template
Save to input/ideas/<slug>-design.md (slug = short, kebab-case, e.g. chronologie-levante-eisen-ii).
---
title: "<Research question in one sentence>"
type: design
created: YYYY-MM-DD
updated: YYYY-MM-DD
tags: [<field>, <region>, <method>]
status: draft
author: mixed
---
# <Title>
## Research Question
A precise, falsifiable or argumentatively testable guiding question.
## Relevance / Forschungsstand (brief)
2–5 sentences: why now, where the debate stands, which gap is addressed.
(Full literature work happens in literature-review — only positioning here.)
## Method
Which approach (*Quellenkritik*, stratigraphic comparison, quantitative
analysis, discourse-analytic reading …). Why this one and not the alternatives.
## Data Sources / Material Basis
Concrete archives, databases, text corpora, excavation publications, datasets.
## Output Target
☐ Book chapter ☐ Journal article ☐ Grant proposal ☐ Talk ☐ Other
## Expected Results
What would a meaningful positive result look like? What a null finding?
## Ethical / Methodological Risks
e.g. access rights to sources, handling of human remains, postcolonial
sensitivity, bias in transmission traditions.
## Feasibility
Time frame, tools (see CLAUDE.md §5), need for collaborators.
## AI-Use Rules
Target institution / venue: <university, journal, publisher, funder — or "open">.
What their rules allow and require (e.g. "AI permitted for language editing and
literature search; disclosure statement in acknowledgements required").
Required disclosure form: statement in text | tool overview page | AI Usage Card | not specified.
Open points: <rules not yet checked — ask supervisor / read author guidelines>.
## Scope Boundaries (what is NOT investigated)
Explicit mention of related questions that fall out of scope.
## Next Step
Hand off to writing-research-plan to produce `input/ideas/<slug>-plan.md`.
The Process
Phase 1 — Understanding the idea:
- Read recent project activity first (existing design docs, log, commits)
- Ask one question per message. Prefer multiple-choice where possible — except for the research question itself, which is open
- Focus: what is the question, what has already been looked at, what would success look like?
- The question comes from the user, Socratically. Before you offer any formulation of your own, ask the user to state what they want to understand and why ("I am investigating X, because I want to understand Y, in order to Z"). A rough sentence, a voice-note transcript or a paragraph of free writing is enough. Then work on their text: ask what a term means, what would count as an answer, which case they have in mind, what they would expect to find. Offer your own variants only after that, as alternatives to compare against theirs — never as the starting point. The reason: formulating the question is the thinking; a polished suggestion that the user merely approves looks like agreement but skips it (automation bias — a machine-made formulation reads as better than one's own and gets accepted unchecked)
- If the user explicitly asks you to propose the question ("schlag du was vor"), do so, but say that the design doc will mark it as agent-proposed until they have reworded or confirmed it in their own words
Phase 2 — Divergent exploration (carried over from scientific-brainstorming):
- Cross-domain analogies (e.g. transferring trade-network analysis from economic history to Iron Age ceramic distribution)
- Assumption reversal ("What if the chronology is the other way around?")
- Scale shifting (single find → site → region → macro-area)
- Interdisciplinary fusion (archaeology + epigraphy + palaeogenetics)
Phase 3 — Critical evaluation:
- What would it take to test this? What's the smallest meaningful sub-experiment?
- Which existing data can be exploited instead of collecting new data?
- Who else would need to be involved (institutions, collaborators)?
Phase 4 — Write, self-review, hand off:
- Write the design doc, run self-review, get sign-off
- Then — and only then — invoke
writing-research-plan
Self-Review Checklist (inline)
After writing the document, look at it with fresh eyes:
- Placeholder scan: "TBD", "to be clarified", "relevant literature" without specifics — replace or delete
- Scope check: Does this fit into ONE research plan, or is it begging to be decomposed?
- Falsifiability: Could the question in principle also be answered in the negative? If not: rephrase
- Ambiguity: Could "Quellenkritik" mean two different methods here? Make it explicit
- Scope boundary: Is there ONE explicit line "not investigated: …"? If not, add one
- AI-use rules: Is the
AI-Use Rulessection filled — or its open points named?
Fix errors inline, no second review pass.
User Review Gate
After self-review:
"Design doc written and saved to
<path>. Please look it over — if changes are needed, give them now. Once you green-light it, we move to writing-research-plan."
Wait for the reply. Only invoke writing-research-plan after approval.
Key Principles
- The user's question first — elicit their formulation before offering yours; your variants sharpen theirs, they don't replace it
- AI-use rules on record — the venue's rules are captured in the design doc, not discovered at submission
- One question per message — don't overload
- Multiple choice preferred — easier to answer
- YAGNI — cut unneeded sub-questions
- Explore alternatives — always offer 2–3 approaches
- Incremental validation — get sign-off section by section
- Stay flexible — go back when something is off
示例提示词
我想申请一个新课题,帮我梳理研究问题、方法可行性和伦理考量。
所属插件
安装该插件会一并获得同领域的 62 个 Skill / MCP。
同插件的其他科研 Skill
- 学术文献获取下载Auto-downloads open-access PDFs for graded sources and writes a manual worklist for paywalled items. Use after literature-review, before ingest-source.
- 单篇文献入库管理Adds one verified PDF to a shared bibliography library, computing its citation key and keywords. Use to register a single document outside the full workflow.
- 数字人文计算方法Surveys computational DH methods: text mining, NLP, corpus linguistics, archive standards, GIS, network analysis, and OCR. Use for an overview of available DH tools.
- 考古地理信息系统分析Runs archaeological GIS analysis with GeoPandas: catchment analysis, viewshed, kernel density, spatial statistics. Use for mapping archaeological site locations.
- 论证结构提取可视化Extracts and visualizes argument structure: Toulmin reconstruction, support/attack graphs, circularity detection. Use to diagram an argument’s logical structure.
- 考古遗物类型学分析Performs artifact analysis: typological classification, ceramic attribute coding, lithic reduction analysis. Use when classifying excavated artifacts statistically.
- 引文与出处核查Checks citations, quotations, page numbers, and bibliography entries for accuracy and source fit. Use before submission to verify source-supported claims.
- 术语译名一致性检查Audits a manuscript for terms, translations, abbreviations, and names whose forms must stay stable. Use when terminology drift could undermine an argument.
- 计算语用学分析Runs computational pragmatics: speech act classification, implicature detection, discourse coherence, politeness analysis. Use for language-use-and-meaning studies.
- 文献综述学术对话构建Turns verified sources into a structured scholarly conversation among positions, not a chronological summary. Use when synthesizing literature into a debate narrative.
- 语料库语言学分析Performs corpus analysis with NLTK/spaCy: collocation, keyword analysis, KWIC concordance, word2vec, diachronic trends. Use for quantitative text-corpus research.
- 数字档案馆资源检索Queries digital archive REST APIs: Europeana, Chronicling America, Internet Archive, HathiTrust, DPLA, OAI-PMH. Use when searching or harvesting heritage metadata.
- 学术手稿章节撰写Drafts a chapter or article section by section from synthesized wiki content, agreeing each section’s argument first. Use to turn stable research synthesis into prose.
- 研究项目漂移状态检测Checks a shared source library and registered projects for drift: un-indexed PDFs, unmerged keywords, bibkey collisions. Use to audit a multi-project research setup.
- EMI课堂语料转写分析Segments and annotates classroom transcripts, coding language choice and discourse function with anonymised output. Use to quantify classroom talk or translanguaging.
- 人工智能伦理分析Analyzes AI ethics: algorithmic fairness metrics, bias auditing, value alignment, moral philosophy reasoning. Use to evaluate an AI system’s ethical dimensions.
- 研究计划任务执行Executes a ready research plan task by task, gating acquisition before ingest and dispatching analysis. Use after writing-research-plan to run the planned work.
- 研究项目结项清单Runs the final completion checklist: rendering, bibliography, wiki, data, reproducibility, archiving. Use when a manuscript is finalized and ready to publish.
- 形式逻辑自动推理Applies formal logic tools: Z3 SMT solver, modal logic S5, SAT encoding, Lean4 proof verification. Use to formalize or mechanically check a logical argument.
- 研究问题凝练构建Turns a broad topic or intuition into a precise, contestable, researchable question. Use at the start of a project when no defensible question yet exists.
- 历史地理信息系统分析Performs historical GIS work: georeferencing old maps, digitizing boundaries, temporal territory overlays, population interpolation. Use for historical spatial analysis.
- 历史语言学比较分析Analyzes historical linguistics in Python: sound correspondences, cognate detection, phylogenetic trees, Swadesh lists. Use when reconstructing language relationships.
- 历史社会网络分析Builds historical network analyses: correspondence networks, prosopography, temporal community detection, Gephi export. Use to map relationships among historical actors.
- 历史文献OCR识别Transcribes printed and handwritten historical documents with Tesseract/Kraken OCR, confidence filtering, spell correction. Use for digitizing scanned historical text.
常见问题
研究选题构思设计能做什么?
Explores research intent, field state, methodology, and ethics, then writes an approved design doc. Use before starting a new research question or chapter。
如何安装研究选题构思设计?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「研究选题构思设计」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
研究选题构思设计需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
研究选题构思设计经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。