amplify

Use when designing the evaluation protocol for a method development project — locks primary metrics, datasets, seeds, statistical tests, and baseline list into an immutable contract

Use when G2 (plan freeze) and G3 (execution readiness) gates have passed — handles all implementation, baseline reproduction, experimentation, and iteration for both Type M and Type D projects; this is Phase 4

Use when research direction is validated (G1 passed) and the project needs method design, analysis framework, evaluation protocol, or story line — this is Phase 3 and must complete before any code or experiments

Reusable protocol for multi-agent discussions that iterate until convergence. Used by results-integration (Phase 5) and paper-writing (Phase 6) to ensure discussions actually resolve issues rather than just noting them.

Use when and ONLY when the user explicitly requests paper writing and G4 (write-ready) gate has passed — handles LaTeX structure, senior-level writing, reference verification, and iterative refinement

Use when Phase 1 (research-direction-exploration) is complete and G1 gate has passed — subjects the research problem to adversarial defense-style questioning, classifies project intent, re-evaluates venue target, and produces a final feasibility ruling before any method design begins

Use when a user expresses research intent but has not yet identified a specific research direction, completed a literature review, or confirmed resource readiness — covers Phase 1 from topic discovery through G1 gate

Use when core experiments or analyses are complete and results need to be organized into a coherent report for user review before paper writing

Use when starting any conversation - establishes how to find and use research skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when a user describes ANY research intent, goal, or topic — this is Phase 0 and must complete before any other research skill activates

Use when analyzing results in Type D or Type H projects before making mechanistic or causal claims — requires systematic exclusion of confounders, batch effects, technical noise, and other alternative explanations

Use when designing the analysis framework for a discovery or data analysis project — defines story line, analysis dimensions, sufficiency criteria, and alternative explanations to check

Use when Phase 4 (experiment execution) begins — enforces complete reporting of all seeds, all results, and all failures; remains active until project end; prevents selective reporting of favorable outcomes

Use when integrating results into a paper or drafting any paper section — enforces that every claim maps to specific evidence before it can be written

Use when facing 2+ independent experiments or tasks that can be worked on without shared state or sequential dependencies

Use whenever generating figures or tables for a research paper — enforces publication-quality visual standards including style consistency, readability, accessibility, and venue-appropriate formatting

Use when evaluation metrics, protocol, datasets, or splits have been confirmed in the research plan — enforces immutability of locked evaluation components without explicit user authorization

Use when assessing innovation level of a research contribution — invoked after literature review (Phase 1) and after method design (Phase 3) to verify that novelty matches the target venue tier

Use when 3 consecutive core experiments or optimizations fail to meet expectations — forces honest status assessment and escalates the pivot/downgrade/kill decision to the user

Use when implementing any experiment, analysis, or computational task — enforces the HYPOTHESIZE-BASELINE-EXPERIMENT-VERIFY-INTERPRET cycle and reproducibility requirements

Use when about to claim ANY research result status — requires running verification, reading full output, and providing evidence before making claims; always active, no exceptions

Use when scope expansion is detected at any phase — enforces focus by quantifying risk and requiring explicit user approval before scope changes

Use when starting research work that needs isolation from current workspace or before executing experiments - creates isolated git worktrees with smart directory selection and safety verification

Use at every gate checkpoint and periodically during experiments to verify that project progress matches the target venue's requirements in terms of experiment scale, novelty depth, and evidence quality