hydromind-research-paper-writing

Orchestrate writer, reviewer, and reviser agents to produce structured research manuscripts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/CMajorChords/HydroMind --skill hydromind-research-paper-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hydromind-research-paper-writing
Source: https://github.com/CMajorChords/HydroMind/tree/main/.agents/skills/hydromind-research-paper-writing
Command: npx skills add https://github.com/CMajorChords/HydroMind --skill hydromind-research-paper-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Hydromind-research-paper-writing orchestrates internal writing agents (writer, reviewer, reviser) to manage the lifecycle of hydromind research manuscripts, ensuring consistent governance, provenance, and phase transitions across outlining, opening, drafting, refinement, and promotion.

Core Features & Use Cases

  • Enables internal paper-life-cycle management by coordinating the writer, reviewer, and reviser subagents built around the hydromind-research-write oracle.
  • Enforces shared doctrine, prompts, and provenance tracking to guarantee traceability and auditability of everyLLM call and decision.
  • Supports lifecycle phases such as outline, opening, figures, draft, refinement, and promote, plus paper-review-v1 and paper-refinement-v2 workflows, including no-reference policy and user citation markers.

Quick Start

Invoke hydromind-research-write with a research task to initialize and guide the paper-writing lifecycle.

Frequently Asked Questions about hydromind-research-paper-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate internal agents for research paper writing?

Research paper writing orchestration coordinates internal writer, reviewer, and reviser subagents to manage manuscript lifecycles. It enforces shared doctrine and provenance tracking to guarantee traceability of every LLM call across outlining, drafting, and refinement phases.

What is LLM workflow provenance tracking for manuscript generation?

LLM workflow provenance tracking records logs and decisions across internal agents during manuscript generation. It enforces per-phase boundaries and traceability, ensuring every writing, reviewing, and revising action is auditable throughout the paper lifecycle.

How do I manage research paper lifecycle phases from outlining to promotion?

Managing research paper lifecycle phases involves guiding internal agents through outline, opening, figures, draft, refinement, and promotion stages. The workflow enforces strict phase transitions and provenance logs to ensure structured manuscript progression and auditability.

Can I enforce a no-reference policy during automated paper drafting?

Yes, automated paper drafting supports a strict no-reference policy alongside user citation markers. Internal writing agents enforce this policy during the draft and refinement phases, ensuring the manuscript adheres to specific citation constraints while maintaining provenance.

Does internal agent workflow orchestration support paper review and refinement?

Internal agent workflow orchestration explicitly supports paper-review-v1 and paper-refinement-v2 workflows. The reviewer and reviser subagents evaluate and enhance drafts, enforcing phase boundaries and provenance tracking to guarantee structured manuscript improvement.

What are the limitations of using internal agents for research writing workflows?

Internal agents for research writing require the specific hydromind-research-write oracle and enforce strict per-phase boundaries. This means workflows are constrained to predefined lifecycle stages and cannot skip provenance logging or bypass the structured outlining to promotion progression.