research-refine-pipeline

# Research Refine Pipeline: End-to-End Method and Experiment Planning Refine and concretize: **$ARGUMENTS** ## Overview Use this skill when the user does not want to stop at a refined method. The goal is to produce a coherent package that includes: - a problem-anchored, elegant final proposal - the review history explaining why the method is focused - a detailed experiment roadmap tied to the paper's claims - a compact pipeline summary that says what to run next This skill composes two existing workflows: 1. `research-refine` for method refinement 2. `experiment-plan` for claim-driven validation planning For stage-specific detail, read these sibling skills only when needed: - `../research-refine/SKILL.md` - `../experiment-plan/SKILL.md` ## Core Rule Do not plan a large experiment suite on top of an unstable method. First stabilize the thesis. Then turn the stable thesis into experiments. ## Default Outputs - `refine-logs/FINAL_PROPOSAL.md` - `refine-logs/REVIEW_SUMMARY.md` - `refine-logs/REFINEMENT_REPORT.md` - `refine-logs/EXPERIMENT_PLAN.md` - `refine-logs/EXPERIMENT_TRACKER.md` - `refine-logs/PIPELINE_SUMMARY.md` ## Workflow ### Phase 0: Triage the Starting Point - Extract the problem, rough approach, constraints, resources, and target venue. - Check whether `refine-logs/FINAL_PROPOSAL.md` already exists and still matches the current request. - If the proposal is missing, stale, or materially different from the current request, run the full `research-refine`...