soloopx.by solo lemon.
Back to loops
Debuggingmanual

Investigation Script Loop

Write a small throwaway script to reproduce a bug, run it, read output, and iterate until the root cause is proven.

0 views0 usesby solo lemon.

// parameters

Triggermanual
Max iterations8
Exit conditionRoot cause demonstrated by script output with a written summary

// run_this_loop

Copy the kickoff into your agent first. The blueprint below explains how the loop evaluates progress and when it should stop.

Open in CursorOpen in Claude

Use loop copies the kickoff prompt. Share copies the loop link. Open in Cursor / Claude only pre-fill that prompt — they do not install hook files. Download loop saves the loop as investigation-script-loop.md.

Start the "Investigation Script Loop" loop.

Goal: prove the root cause with a minimal repro script
Max iterations: 8
Between iterations run: node scripts/investigate.mjs
Exit when: script output demonstrates root cause

Step 1: Write a tiny throwaway script that reproduces the issue. Run it and iterate on what the output shows.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

// blueprint

The loop contract: target outcome, execution sequence, checks, stopping condition, and safety constraints.

Goal

prove the root cause with a minimal repro script

// loop_sequence

// loop_sequence_diagram.json
closed loop

Trigger

Manual start

Actions block

3 steps
1Write probe script
2Run and read
3Adjust hypothesis

Feedback gate

Evaluate: state progress

Run the check, read the output, then decide whether the loop is complete.

Check failed

Repeat actions with the latest feedback.

Success

Root cause demonstrated by script output with a written summary

Safety capMax 8 iterations

// steps

  1. 1
    Write probe script

    Create a ~20-line script that reproduces the bug or queries the failing state. One file only.

  2. 2
    Run and read

    Execute the script and capture stdout/stderr. No guessing — read actual output.

  3. 3
    Adjust hypothesis

    Update the script or notes based on output. Stop when root cause is demonstrated.