Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for user experience designers

Prototype Iteration Change Log Agent

A traceable log where every design change links to a test finding and every finding has a verified outcome

Quality controlAutomationCreativesProduct development
See how it worksGet access
Prototype Iteration Change Log Agent: what goes in, what the agent does and what you get

What it does

Version 4 of a prototype has six changes, but nobody remembers which test finding each change was for, or whether the problem it addressed was actually solved. After each test session, this agent reads the findings, such as 'handle slips when wet' or 'hinge feels loose', and links them to the design changes planned for the next build. When the next version is tested, it checks whether each earlier finding was resolved, partly resolved or still open, using new test notes and measurements. Open findings loop back to the plan. It maintains a log with finding, change, version and result, so reviewers can see why every change was made. The designer approves the next build list. Edge case: a change made with no matching finding is flagged as untraced so the team can decide if it was needed.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueApprovedYes, continueNoNo 1 STARTS WHEN Test session completes 2 USES A TOOL Read the new test notes and measurements 3 DOES Extract findings and rate their severity 4 USES A TOOL Read the previous log and the changes made forearlier findings 5 CHECKS THE RESULT Does the new data show each earlier findingresolved, partial or open? If not: Ask the tester for the missing note and reviewthe data again. Back to step 3. 6 DOES Link new findings to proposed changes for the nextbuild 7 DOES Flag changes with no linked finding 8 YOU APPROVE Designer approves the next build list 9 USES A TOOL Update the change log with versions and results 10 CHECKS THE RESULT Is every open finding either in the next build listor deferred with a reason? If not: Add the finding to the plan or ask the designerfor a deferral reason. Back to step 6. 11 RESULT Updated change log
Read the steps as a list
  1. Test session completes
  2. Read the new test notes and measurements
  3. Extract findings and rate their severity
  4. Read the previous log and the changes made for earlier findings
  5. Does the new data show each earlier finding resolved, partial or open?If not: Ask the tester for the missing note and review the data again. Back to step 3.
  6. Link new findings to proposed changes for the next build
  7. Flag changes with no linked finding
  8. Designer approves the next build listThe agent waits here for your OK.
  9. Update the change log with versions and results
  10. Is every open finding either in the next build list or deferred with a reason?If not: Add the finding to the plan or ask the designer for a deferral reason. Back to step 6.
  11. Updated change log

How it decides

A finding is resolved only if the next test notes show the issue gone or the measurement within spec. Partial results stay open with the evidence attached.

  • Mark a finding resolved only with test evidence
  • Keep partial results open
  • Flag any change without a linked finding
  • Order the next build list by severity then effort

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Severity scale
  • Evidence needed to resolve a finding
  • Test note format
  • Log location
  • Who approves build lists

What keeps you in control

It always asks you first

  • Designer approves the next build list and any deferral

Hard limits

  • Never mark a finding resolved without evidence
  • Never change the design files

It stops when

  • Done: All findings have a status and all changes are traced
  • Stop: Test notes are too thin to judge findings, so the agent asks for another test

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensAfter test 4, the log shows finding F7, handle slips when wet. Version 4 added a rubber grip. The new notes say 3 of 8 testers still slipped, so the agent keeps F7 partial. Finding F9, loose hinge, is resolved with 8 of 8 passes. A change to a button color has no finding and is flagged. The designer approves the next build.

More agents for user experience designers

Compliance · Automation

Prototype Usability Session Agent

Consistent, consent-respecting usability session records.

9 steps2 checks3 jobs
Analysis · Product development

Product Onboarding Friction Agent

Onboarding friction traced to its real cause.

8 steps1 check4 jobs
Creating · Quality control

Prototype Interaction State Agent

Prototypes that cover errors and recovery, not just the happy path.

8 steps2 checks3 jobs
Document handling · Automation

Design Decision Log and Rationale Agent

Keep a decision log where every design choice has an owner, options and linked evidence.

10 steps2 checks3 jobs