hydromind-research-design
Stage 1 canonicalization sub-skill of the HydroMind Research family. Materialize an integrated study design as the canonical `research/<research_id>/study_design.json` after explore mode (or a substantive design conversation) has produced enough shared understanding. This skill is the Stage 1 ONLY writer of `study_design.json`; `hydromind-research-explore` stays read-only on canonical state and must hand off here. Use this whenever the researcher says "ok let's write that down", "make this the design", "update the design", "canonicalize the study design", or otherwise signals that a discussed design should become canonical state - even without the word "propose". Use this AFTER `hydromind-research-explore` (or equivalent design discussion). After `study_design.json` is validated, hand off to `hydromind-research-execution` (drafting-blocking evidence gaps remain) or `hydromind-research-paper` (no drafting-blocking gaps remain).
Repository SourceNeeds Review
hydromind-research-explore
Stage 1 main skill of the HydroMind Research family. Enter integrated study exploration - a thinking partner that helps the researcher firm up "what experiments to run AND what paper to tell" together, grounded in the existing `research/<research_id>/` workspace (`context.json`, `draft.md`, optional existing `study_design.json`, optional `paper/inputs/experimental_log.md`). Use this whenever the researcher is unsure what the next paper should claim, which evidence gaps still block drafting, which literature clusters must be covered, what figures the paper needs, or how Methods/Experiments/Discussion should be framed - even if they don't explicitly say "design" or "explore". Use this BEFORE `hydromind-research-design` materializes `study_design.json`, and BEFORE `hydromind-research-execution` commits to a new batch of runs. This skill MUST stay read-only on canonical state.
Repository SourceNeeds Review
hydromind-research-paper
Stage 3 main skill of the HydroMind Research family. Drive a research paper from a validated `study_design.json` through the canonical `paper/` subworkspace - projecting `paper/inputs/idea.md` and `paper/outline.json` from the design, building the verified literature pool, preparing figures, producing a constrained unified draft, and running accept/revert/halt refinement to a `final/paper.md`. Use this whenever the researcher wants to "start the paper", "do literature for the paper", "draft the paper", "refine the paper", "finalize the manuscript", or otherwise advance any phase of the paper pipeline - even without the word "workflow". Use this AFTER `hydromind-research-design` has written and validated `study_design.json` with no drafting-blocking evidence gaps (otherwise route to `hydromind-research-execution` first). Inside drafting (Phase 4) and refinement (Phase 5), defer prose-quality decisions to the internal sub-skill `hydromind-research-paper-writing`; deterministic gates (literature verification, ci
Repository SourceNeeds Review
hydromind-research-paper-writing
Stage 3 internal prose-quality sub-skill of the HydroMind Research family. Improve prose quality of an ML/CV/NLP-style paper draft — section structure, paragraph flow, claim-evidence alignment, and reviewer-facing presentation. Loaded by `hydromind-research-paper` Phase 4 (unified drafting) and Phase 5 (refinement) to handle the writing-craft layer. MUST NOT be invoked standalone for HydroMind research-to-paper work, because deterministic gates (literature verification, citation coverage, anti-leakage, refinement decision/halt) live in `hydromind-research-paper` and must not be bypassed. If a researcher asks for paper help without going through `hydromind-research-paper` first, route through the parent workflow.
Repository SourceNeeds Review