Document that something worked in one release and broke in the next

Draft before-and-after regression material covering scope and missing comparison tests.

Choose one of three approaches. The steps for that option appear below.

Choose an option above. On a phone, swipe the tabs left or right to see all options →

Claude: aligns the releases and drafts, you check

Claude builds the release comparison table, then drafts the regression material in the same chat. You check both stages.

  1. You

    Collect the case files

  2. Claude

    Align the releases

  3. You

    Check the worksheet

  4. Claude

    Draft the scope

  5. You

    Check and decide

  1. Have ready: customer cases, release evidence, approved rules

    Use: You

    The customer cases, the supplied release comparison evidence, and the approved rules, scope and as-of dates.

    Check

    Check nothing needed for the task was removed and source IDs are unchanged. Never paste credentials or full payment details.

  2. Align steps and outcomes by release

    Use: Claude

    Upload the files to one Claude chat; ask it to align comparable steps and outcomes by release in one table, returned as chat text.

    Details

    What to paste into the tool

    Task: Evidence worksheet as a table in the chat reply with row IDs, source references, original values, status and unresolved gaps. Attached are the supplied files. Build a worksheet: one row per item, stable row ID, source file and location, exact quote or original value, applicable rule or version, confirmed or reported status, unresolved gap. Align comparable steps and outcomes by release in separate columns. Give every difference its version evidence. Do not state a cause; correlation is not cause. Use only the supplied files. Keep every source ID, quote or original value, rule or version reference and as-of date exactly as supplied. List anything missing, contradictory or unchecked as unresolved; do not fill gaps by inference. Do not repeat passwords, authentication codes, session tokens or payment details, and keep customer details to the minimum needed. If sources or a qualified reviewer are missing, label the output incomplete. Do not send, publish, assign, execute or commit anything. Return the worksheet as a table in the chat reply; do not create or return a file and do not run code.

  3. Check the worksheet and correct it

    Use: You

    Check every worksheet row against the originals and correct it.

    Check

    Check claims, values, chronology and rule applicability against the originals for this case: Workflow worked before an update and now fails. Do not fill missing or contradictory facts by inference.

  4. Draft the regression scope and missing tests

    Use: Claude

    In the same chat, ask for the regression scope and missing comparison tests from the corrected worksheet.

    Details

    What to paste into the tool

    Task: Draft before-and-after regression packet; Explicit unresolved questions and a proposed next human decision, not an executed action. Using only the corrected worksheet, draft the before-and-after regression packet. Scope the regression, list missing comparison tests, give version evidence for each difference and do not assert a cause. State unresolved questions and a proposed next human decision; do not execute or commit anything. Use only the supplied files. Keep every source ID, quote or original value, rule or version reference and as-of date exactly as supplied. List anything missing, contradictory or unchecked as unresolved; do not fill gaps by inference. Do not repeat passwords, authentication codes, session tokens or payment details, and keep customer details to the minimum needed. If sources or a qualified reviewer are missing, label the output incomplete. Do not send, publish, assign, execute or commit anything. Return the draft as chat text; do not create or return a file and do not run code.

  5. Check the draft and decide next steps

    Use: You

    Check the draft against the originals and decide what, if anything, happens next.

    Check

    Check each difference has version evidence; correlation is not asserted as cause. Confirm the evidence and draft; completion is preparation, not downstream execution. Check the draft text stays inside the worksheet rows. Nothing is sent, filed, assigned or committed by this path; any later action is approved separately.

Before you paste into any AI tool, remove any confidential information. Put it back at the end.

Tools in this workflow

Deciding between ChatGPT and Claude for this? See the comparison.

Final check

Never paste credentials or full payment details.

Reviewer checks every row and statement against the supplied originals.

No password, code, token or payment detail is entered or reproduced.

Missing or contradictory facts stay marked as unresolved.

Nothing is sent, filed, assigned or committed; any later action needs separate approval.

Each difference carries version evidence and correlation is not asserted as cause.

Suggestions and preparation only. Do not send, publish, change records or accounts, assign work, execute code, initiate a purchase, or commit a remedy or deadline. A human separately approves any downstream action.

Check the result against your original inputs. Approve it before sharing or acting.

What still needs checking
  • Whether the release comparison evidence supplied is complete for the workflow in question
  • Which customer cases the engineer treats as in scope

Share this page