research-refine

Refine vague research directions into implementation-ready method plans.

Updated May 29, 2026
One-click install
npx skills add https://github.com/Mang30/myskills --skill research-refine-mang30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-refine
Source: https://github.com/Mang30/myskills/tree/main/skills/research-refine
Command: npx skills add https://github.com/Mang30/myskills --skill research-refine-mang30

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, Agent, mcp__codex__codex, mcp__codex__codex-reply.

What problem does it solve?

Helps convert a vague research direction into a concrete, implementation-oriented research plan anchored to the original problem, with minimal validation experiments and frontier-aware method choices.

Core Features & Use Cases

  • Problem Anchor Preservation: Freezes an immutable problem statement and carries it verbatim through iterative refinement rounds to prevent drift.
  • Method-First, Elegance-First Planning: Produces a focused proposal with a single dominant mechanism, clean system integration, and explicit training/inference paths.
  • Frontier-Aware Review Loop: Runs iterative reviews to improve fidelity, specificity, contribution quality, and appropriate use of modern foundation-model-era primitives.
  • Checkpoint Recovery & Full Logs: Persists state to recover from interruptions and saves round-by-round artifacts for auditability.

Use cases: refining an approach you already know is on the right track but still “fuzzy,” decomposing a research idea into a paper-ready method, and producing a top-venue style plan without turning it into an overbuilt benchmark campaign.

Quick Start

Use the research-refine skill by telling it your bottom-line problem and the vague approach you currently have, for example: refine my approach to solve [problem] using [high-level idea] so that the result is implementation-oriented, elegant, and frontier-aware.

Frequently Asked Questions about research-refine

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

FAQPage Schema
How do I turn a vague research idea into an implementation-ready method plan?

To turn a vague research idea into an implementation-ready method plan, you need iterative problem framing and method-first proposal writing. This process anchors your original problem and refines the technical route into concrete system, thesis, training, and inference specifications.

What is the best way to refine experiment design for foundation-model-era research?

The best way to refine experiment design for foundation-model-era research is through a frontier-aware review loop. This method evaluates your proposal for fidelity, specificity, and contribution sharpness while ensuring appropriate use of modern foundation-model primitives.

How do I prevent problem drift during iterative research refinement?

To prevent problem drift during iterative research refinement, use problem anchor preservation. This technique freezes an immutable problem statement and carries it verbatim through each review round to ensure the technical route remains anchored to the original core issue.

Can I use WebSearch to ground research method planning in existing literature?

Yes, you can use WebSearch and WebFetch for literature grounding during research method planning. Integrating web search allows you to validate your problem framing against existing literature and incorporate frontier-aware machine learning techniques into your refined plan.

Does this iterative review process support checkpoint recovery for long research sessions?

Yes, the iterative review process supports checkpoint recovery by persisting state across rounds. This allows you to recover from interruptions and maintains round-by-round artifact logs for full auditability of your method-first proposal writing.

When should I not use method-first proposal writing for research refinement?

You should not use method-first proposal writing when your core problem is completely invisible or when you need an overbuilt benchmark campaign instead of an elegant plan. It specifically applies when the problem is visible but the technical route remains unclear.