solve-bridge

name	solve-bridge
description	Workflow 1.5: 从求解计划到代码实现的桥梁。读取 SOLVE_PLAN.md，实现求解代码，本地执行，收集初始结果。当用户说'实现求解'、'写代码'、'bridge'、'从计划到求解'时使用。
argument-hint	["solve-plan-path-or-topic"]
allowed-tools	Bash(*), Read, Write, Edit, Grep, Glob, Agent, Skill, mcp__codex__codex, mcp__codex__codex-reply

Workflow 1.5: Experiment Bridge

Implement and deploy experiments from plan: $ARGUMENTS

Overview

This skill bridges Workflow 1 (idea discovery + method refinement) and Workflow 2 (auto review loop). It takes the experiment plan and turns it into running experiments with initial results.

Workflow 1 output:                    This skill:                                    Workflow 2 input:
refine-logs/SOLVE_PLAN.md   →   implement → GPT-5.4 review → deploy → collect → initial results ready
refine-logs/SOLVE_TRACKER.md     code        (cross-model)    /run-solver     for /auto-optimize-loop
refine-logs/FINAL_PROPOSAL.md

Constants

• CODE_REVIEW = true — GPT-5.4 xhigh reviews experiment code before deployment. Catches logic bugs before wasting GPU hours. Set false to skip.
• AUTO_DEPLOY = true — Automatically deploy experiments after implementation + review. Set false to manually inspect code before deploying.
• SANITY_FIRST = true — Run the sanity-stage experiment first (smallest, fastest) before launching the rest. Catches setup bugs early.
• MAX_PARALLEL_RUNS = 4 — Maximum number of experiments to deploy in parallel (limited by available GPUs).
• BASE_REPO = false — GitHub repo URL to use as base codebase. When set, clone the repo first and implement experiments on top of it. When false (default), write code from scratch or reuse existing project files.
• COMPACT = false — When true, (1) read MODEL_CANDIDATES.md instead of full MODEL_REPORT.md if available, (2) append experiment results to EXPERIMENT_LOG.md after collection.

Override: /solve-bridge "SOLVE_PLAN.md" — compact: true, base repo: https://github.com/org/project

Inputs

This skill expects one or more of:

1. refine-logs/SOLVE_PLAN.md (best) — claim-driven experiment roadmap from /solve-plan
2. refine-logs/SOLVE_TRACKER.md — run-by-run execution table
3. refine-logs/FINAL_PROPOSAL.md — method description for implementation context
4. MODEL_CANDIDATES.md — compact idea summary (preferred when COMPACT: true)
5. MODEL_REPORT.md — full brainstorm output (fallback)

If none exist, ask the user what experiments to implement.

Workflow

Phase 1: Parse the Experiment Plan

Read SOLVE_PLAN.md and extract:

1. Run order and milestones — which experiments run first (sanity → baseline → main → 灵敏度分析 → polish)
2. For each experiment block:
   • Dataset / split / task
   • Compared systems and variants
   • Metrics to compute
   • Setup details (backbone, hyperparameters, seeds)
   • Success criterion
   • Priority (MUST-RUN vs NICE-TO-HAVE)
3. Compute budget — total estimated compute-minutes
4. Method details from FINAL_PROPOSAL.md — what exactly to implement

Present a brief summary:

📋 Experiment plan loaded:
- Milestones: [N] (sanity → baseline → main → 灵敏度分析)
- Must-run experiments: [N]
- Nice-to-have: [N]
- Estimated compute-minutes: [X]

Proceeding to implementation.

Phase 2: Implement Experiment Code

If BASE_REPO is set — clone the repo first:

git clone <BASE_REPO> base_repo/
# Read the repo's README, understand its structure, find entry points
# Implement experiments by modifying/extending this codebase

For each milestone (in order), write the experiment scripts:

1. Check existing code — scan the project (or cloned base_repo/) for existing experiment scripts, model code, data loaders. Reuse as much as possible.

2. Implement missing pieces:

   • Training scripts with proper argparse (all hyperparameters configurable)
   • Evaluation scripts computing the specified metrics
   • Data loading / preprocessing if needed
   • Baseline implementations if not already present
   • Fixed random seeds for reproducibility
   • Results saved to JSON/CSV for later analysis
   • Proper logging (wandb if configured in CLAUDE.md)

3. Follow the plan's run order — implement sanity-stage experiments first, then baselines, then main method, then 灵敏度分析s.

4. Self-review before deploying:

   • Are all hyperparameters from SOLVE_PLAN.md reflected in argparse?
   • Is the random seed fixed and controllable?
   • Are results saved in a parseable format (JSON/CSV)?
   • Does the code match FINAL_PROPOSAL.md's method description?

Phase 2.5: Cross-Model Code Review (when CODE_REVIEW = true)

Skip this step if CODE_REVIEW is false.

Before deploying, send the experiment code to GPT-5.4 xhigh for review:

mcp__codex__codex:
  config: {"model_reasoning_effort": "xhigh"}
  prompt: |
    Review the following experiment implementation for correctness.

    ## Experiment Plan:
    [paste key sections from SOLVE_PLAN.md]

    ## Method Description:
    [paste from FINAL_PROPOSAL.md]

    ## Implementation:
    [paste the experiment scripts]

    Check for:
    1. Does the code correctly implement the method described in the proposal?
    2. Are all hyperparameters from the plan reflected in the code?
    3. Are there any logic bugs (wrong loss function, incorrect data split, missing eval)?
    4. Is the evaluation metric computed correctly?
    5. **CRITICAL: Does evaluation use the dataset's actual ground truth labels — NOT another model's output as ground truth?** This is a common and severe bug.
    6. Any potential issues (OOM risk, numerical instability, missing seeds)?

    For each issue found, specify: CRITICAL / MAJOR / MINOR and the exact fix.

On review results:

• No CRITICAL issues → proceed to Phase 3
• CRITICAL issues found → fix them, then re-submit for review (max 2 rounds)
• Codex MCP unavailable → skip silently, proceed to Phase 3 (graceful degradation)

Phase 3: Sanity Check (if SANITY_FIRST = true)

Before deploying the full experiment suite, run the sanity-stage experiment:

/run-solver [sanity experiment command]

Wait for completion. Verify:

• Training loop runs without errors
• Metrics are computed and saved correctly
• GPU memory usage is within bounds
• Output format matches expectations

If sanity fails → fix the code, re-run. Do not proceed to full deployment with broken code.

Phase 4: Deploy Full Experiments

Deploy experiments following the plan's milestone order:

/run-solver [experiment commands]

For each milestone:

1. Deploy experiments in parallel (up to MAX_PARALLEL_RUNS)
2. Use /monitor-solver to track progress
3. Collect results as experiments complete

🚦 Checkpoint (if AUTO_DEPLOY = false):

🔧 Code implementation complete. Ready to deploy:

Milestone 0 (sanity): [status — passed/pending]
Milestone 1 (baseline): [N experiments, ~X compute-minutes]
Milestone 2 (main method): [N experiments, ~X compute-minutes]
Milestone 3 (灵敏度分析s): [N experiments, ~X compute-minutes]

Total estimated: ~X compute-minutes on [N] GPUs

Deploy now? Or review the code first?

Phase 5: Collect Initial Results

As experiments complete:

1. Parse output files (JSON/CSV/logs) for key metrics
2. Training quality check — if W&B data is available (CLAUDE.md has wandb: true and wandb_project), invoke /training-check to detect NaN, loss divergence, plateaus, or overfitting. If W&B is not configured, skip silently.
3. Update refine-logs/SOLVE_TRACKER.md — fill in Status and Notes columns
4. Check success criteria from SOLVE_PLAN.md — did each experiment meet its bar?
5. Write initial results summary:

# Initial Experiment Results

**Date**: [today]
**Plan**: refine-logs/SOLVE_PLAN.md

## Results by Milestone

### M0: Sanity — PASSED
- [result]

### M1: Baselines
| Run | System | Key Metric | Status |
|-----|--------|-----------|--------|
| R001 | baseline_1 | X.XX | DONE |

### M2: Main Method
| Run | System | Key Metric | Status |
|-----|--------|-----------|--------|
| R003 | our_method | X.XX | DONE |

### M3: Ablations
...

## Summary
- [X/Y] must-run experiments completed
- Main result: [positive/negative/inconclusive]
- Ready for /auto-optimize-loop: [YES/NO]

## Next Step
→ /auto-optimize-loop "[topic]"

Phase 5.5: Write Compact Log (when COMPACT = true)

Skip entirely if COMPACT is false.

Append each completed experiment to EXPERIMENT_LOG.md:

## [Run ID] — [timestamp]
- **System**: [method name]
- **Config**: [key hyperparameters]
- **Result**: [primary metric = X.XX]
- **Verdict**: [positive / negative / inconclusive]
- **Reproduce**: `python train.py --config configs/run_id.yaml --seed 42`

This structured log survives session recovery — downstream skills read it instead of parsing screen output.

Phase 5.6: Auto Ablation Planning

After main experiments (M2) complete with positive results, invoke /灵敏度分析-planner to design 灵敏度分析 studies:

• Read the main results and method description
• Generate a claim-driven 灵敏度分析 plan: which components to remove, what to compare, expected outcomes
• Append 灵敏度分析 blocks to refine-logs/SOLVE_PLAN.md and refine-logs/SOLVE_TRACKER.md
• If main results are negative or inconclusive, skip 灵敏度分析 planning and note in the summary

If /灵敏度分析-planner is not available, skip silently — the existing SOLVE_PLAN.md 灵敏度分析 blocks (if any) remain unchanged.

Phase 6: Handoff

Present final status:

🔬 Experiment bridge complete:
- Implemented: [N] experiment scripts
- Deployed: [N] experiments on [M] GPUs
- Completed: [X/Y] must-run, [A/B] nice-to-have
- Main result: [one sentence]

Results: refine-logs/EXPERIMENT_RESULTS.md
Tracker: refine-logs/SOLVE_TRACKER.md

Ready for Workflow 2:
→ /auto-optimize-loop "[topic]"

Key Rules

• Large file handling: If the Write tool fails due to file size, immediately retry using Bash (cat << 'EOF' > file) to write in chunks. Do NOT ask the user for permission — just do it silently.
• CRITICAL — Evaluation must use dataset ground truth. When writing evaluation scripts, ALWAYS compare model predictions against the dataset's actual ground truth labels/targets — NEVER use another model's output as ground truth. Double-check: (1) ground truth comes from the dataset split, not from a baseline/backbone model, (2) evaluation metrics are computed against the same ground truth for all methods, (3) if the task has official eval scripts, use those.
• Follow the plan. Do not invent experiments not in SOLVE_PLAN.md. If you think something is missing, note it but don't add it.
• Sanity first. Never deploy a full suite without verifying the sanity stage passes.
• Reuse existing code. Scan the project before writing new scripts. Extend, don't duplicate.
• Save everything as JSON/CSV. The auto-optimize-loop needs parseable results, not just terminal output.
• Update the tracker. SOLVE_TRACKER.md should reflect real status after each run completes.
• Don't wait forever. If an experiment exceeds 2x its estimated time, flag it and move on to the next milestone.
• Budget awareness. Track compute-minutes against the plan's budget. Warn if approaching the limit.

Composing with Other Skills

/modeling-discovery "direction"          ← Workflow 1: find + refine + plan
/solve-bridge                   ← you are here (Workflow 1.5: implement + deploy)
/auto-optimize-loop "topic"            ← Workflow 2: review + iterate
/paper-writing "MODELING_NARRATIVE.md" ← Workflow 3: write the paper

Or use /mathmodel-pipeline for the full end-to-end flow (includes this bridge).