From 6689a3bba88a29a9d4f7706ef9fd413fe21d88bf Mon Sep 17 00:00:00 2001 From: Sven Date: Wed, 25 Mar 2026 22:56:43 +0100 Subject: [PATCH] fix(fix-loop): add explicit rejection/revision loop to Plan Mode setup MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adds a step 5 handling block to Phase 1 so users can approve, request changes (looping back through parameter gathering), or cancel — closing the audit gap in §8 Plan Mode where no rejection path existed. Co-Authored-By: Claude Sonnet 4.6 --- templates/commands/maxsim/fix-loop.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/templates/commands/maxsim/fix-loop.md b/templates/commands/maxsim/fix-loop.md index ce927fc0..9a14a70b 100644 --- a/templates/commands/maxsim/fix-loop.md +++ b/templates/commands/maxsim/fix-loop.md @@ -31,8 +31,12 @@ Invoke the `autoresearch` skill (fix workflow) to drive the repair loop. Invoke - **Iteration budget** — max fix attempts before stopping (default: 30) - **Scope** — which files/directories are in-scope for modification (default: auto-detect from errors) 3. Run the error command once to establish the baseline error count -4. Show the proposed loop configuration, baseline error count, and confirm with user -5. Exit Plan Mode via ExitPlanMode +4. Show the proposed loop configuration, baseline error count, and ask user to confirm +5. **Handle user response:** + - **If user approves:** proceed to step 6 + - **If user requests changes:** return to step 2 to re-gather the modified parameters (stay in Plan Mode). If the error command changed, re-run it for a new baseline (step 3). Re-show the revised configuration and confirm again. + - **If user cancels:** Exit Plan Mode via ExitPlanMode and stop — do not start the fix loop. +6. Exit Plan Mode via ExitPlanMode **Phase 2 — Fix Loop**