Plan First, Then Verify Each Step
It makes the AI investigate and agree a plan before touching your code, then prove each fix with real checks. Giving it clear pass or fail targets stops it declaring victory as soon as the code merely compiles.
The prompt
Act as a careful senior software engineer who never calls a job finished until it has been checked.
Task: Fix the problem described below in the codebase. Do not change any code until I approve your plan.
Problem file: {file_name}
Symptom: {symptom}
Expected behaviour: {expected_behaviour}
Checks that must pass: {verification_checks}
Steps:
1. Explore read-only first. Read the relevant files and trace the cause. Do not edit anything yet.
2. Write a short numbered plan of the changes, naming each file, and stop so I can review it.
3. After I approve, make the changes one step at a time, running the relevant check after each step.
4. Run every item in the checks list and report the actual result of each, not an assumption.
5. If any check fails, diagnose and fix it, then run all the checks again.
Output: First reply: a "Findings" paragraph and the numbered plan only. Final reply: a table of each check with PASS or FAIL and the evidence, then a list of files changed with one line on why.
Change the parts in curly braces. Use it for bugs or changes that touch several files, where a quick one-line fix request would tempt the AI to guess.
What happened when we ran it
We sent
Act as a careful senior software engineer who never calls a job finished until it has been checked. Task: Fix the problem described below in the codebase. Do not change any code until I approve your plan. Problem file: src/middleware/auth.js Symptom: Logged-in users are redirected to /login every time they refresh the dashboard page. The session cookie is set correctly in the browser, but the server seems to ignore it. This started after we added the rate limiter last week. Expected behaviour: A user with a valid session cookie stays on the dashboard after a refresh and receives a 200 response. A user without a cookie is still redirected to /login. Checks that must pass: Run npm test and confirm all tests in tests/auth.test.js pass. Confirm the session middleware is registered before the rate limiter in src/app.js. Request /dashboard with curl using a valid cookie and confirm a 200 response. Steps: 1. Explore read-only first. Read the relevant files and trace the cause. Do not edit anything yet. 2. Write a short numbered plan of the changes, naming each file, and stop so I can review it. 3. After I approve, make the changes one step at a time, running the relevant check after each step. 4. Run every item in the checks list and report the actual result of each, not an assumption. 5. If any check fails, diagnose and fix it, then run all the checks again. Output: First reply: a "Findings" paragraph and the numbered plan only. Final reply: a table of each check with PASS or FAIL and the evidence, then a list of files changed with one line on why.
The model replied
Run on Claude Sonnet 5.5, 10 Nov 2026. Automatic check: 2 out of 5.
Mentioned for
Claude Code, Claude, ChatGPT, Cursor
Where it came from
Found on Web, shared by Josphat Mutai (ComputingForGeeks), updated 9 Nov 2026: Claude Code Cheat Sheet: Commands, Shortcuts and Flags.
This is our own version of the idea, written and tested by us. The original may differ.