plan-next

You are running the user's /plan-next command. Your job is to PROPOSE the next experiments from evidence; the user's job is to DECIDE. Never launch anything from this command without an explicit go.

Steps

1. Establish scope: which experiment/topic is being planned? If unclear, ask.

2. Read the evidence, in this order:

   • docs/plans/<topic>.md if it exists (the standing plan);
   • docs/exp/<slug>/findings.md (established results + failed attempts — never propose something the Failed Attempts table already rules out);
   • docs/exp/<slug>/journal.md and mcp__projtool__compare_runs (experiment_id=...) for the actual numbers;
   • the newest reports under docs/exp/<slug>/ and docs/summary/.

3. Ensure the plan document exists at docs/plans/<topic>.md. If absent, create it with this skeleton (in the docs repo):

   # Plan — <topic>
   
   ## Hypothesis
   <what we believe and want to test>
   
   ## Decision criteria
   <metric + threshold that settles it, e.g. "adopt if val_acc > baseline + 0.5pt">
   
   ## Experiment matrix
   | id | config / command | seeds | status | result |
   |---|---|---|---|---|
   
   ## Next up (proposed — human approves before launch)
   
   ## Decided / archived
   

4. Propose 1-3 next experiments, each with:

   • what it tests (tie it to the Hypothesis / an Open question in findings);
   • exact shape: config file(s) or run_script command, seeds, GPU spec, and a rough cost (hours × instance);
   • the decision criterion it feeds. Write them into the plan's "Next up" section and show the user.

5. Stop and ask the user to pick. After they choose:

   • queue config sweeps via mcp__projtool__start_runs(configs=[...]);
   • single/vendored jobs via start_training / run_script;
   • update the matrix rows to status=running, and commit the plan file in the docs repo (git add docs/plans/<topic>.md && git commit).

6. When results land later (finalize + journal), a future /plan-next pass moves matrix rows to status=done with the result and prunes "Next up".

Keep the plan short-lived and honest: it is a working document, not a proposal to impress anyone. One page max.