Eureka

Use during or after manuscript writing to verify every quantitative claim traces to actual data, every figure is script-generated, and all results including negative ones are reported

Use when starting any conversation involving research, hypotheses, experiments, data analysis, scientific claims, or manuscript writing — establishes how to find and use Eureka research skills

Use when a research design has been approved and needs to be broken into executable experiment steps — the research equivalent of an implementation plan

Use when creating, updating, or reviewing a research figure (plot, chart, brain map, heatmap, schematic) — guides chart-type selection, typography, colorblind-safe palette, layout, and journal-specific export specs. Dispatches a figure-reviewer subagent after rendering. Complements claims-audit (which checks figure integrity) by checking figure design.

Use when running any experiment or analysis — hypothesis and analysis plan must be registered before seeing results, the scientific equivalent of test-driven development

Use when writing a research manuscript — guides section-by-section writing with prerequisite gates, citation discipline, number traceability, and per-section subagent review. Activated after experiment results are reviewed and before claims-audit.

Use when an experiment phase is complete, before drawing conclusions, before writing results, or before claiming findings are publication-ready

You MUST use this before any experiment, analysis, or scientific claim — when a research question, hypothesis, study design, or scientific approach needs to be defined or refined

Use when research work is complete and you need to decide the next step — submit to journal, share as preprint, continue refining, or pivot direction

Use before claiming results are publication-ready, before submitting manuscripts, or before sharing findings externally — requires fresh verification evidence for every claim

Use when a researcher is stuck, unsure of the next step, feels lost in the middle of a project, or asks any variant of "what should I do next?", "where am I?", "what now?", "I'm stuck" — diagnoses research state and recommends which Eureka skill to invoke next

Use before submission to verify the manuscript's contribution is still novel and competitive against recent literature (last 2 years) — 출판 전 경쟁 검토, preemption 체크, novelty 감사. Detects preemption, re-verifies contribution altitude, runs a differentiation test, and issues PASS/CONCERN/BLOCK. Complements research-brainstorming Step 3 (design-time novelty) at submission time.

Use when the researcher has no specific research question yet — when they need to discover what to study, not how to study it. Triggers on keywords like 'what should I research', 'research ideas', 'what can I do with this dataset', or when a dataset/paper is provided without a formed question.

Use when finishing a research work session, after making a significant methodological decision, after a failed experiment or unexpected result, before a phase transition, or when the user explicitly asks to log/memo/remember the session — appends a structured narrative entry to docs/eureka/journal/ capturing decisions, failures, surprises, blockers, and next-session starting points

Use when receiving research review feedback, before implementing suggestions — requires verification against actual data and scientific reasoning, not performative agreement

Use when experiments produce unexpected results, analyses fail, or findings contradict expectations — before proposing explanations or re-running