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 qa managers

Product Requirement Change Impact Agent

Every requirement change reaches all linked tests, docs and teams.

Product Requirement Change Impact Agent: what goes in, what the agent does and what you get

What it does

When a product requirement changes, linked tests, documents and dependent teams often miss the update. When a requirement revision is approved, this agent follows the traceability links to every acceptance criterion, test, help article and team that depends on it. It drafts updates and creates tasks for each owner. After owners report back, it runs coverage checks to confirm each dependent item now matches the new requirement. Any item still out of date gets a new task. Tests that still check removed behavior are flagged. It retires only items explicitly made obsolete. Product operations approves scope and acceptance changes. Edge case: two linked tests still require a removed export option, so tasks are created to update them.

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, continueApprovedNo 1 STARTS WHEN Requirement revised 2 USES A TOOL Trace linked acceptance criteria and artifacts 3 USES A TOOL Create draft updates and owner tasks 4 USES A TOOL Run coverage checks 5 CHECKS THE RESULT Is every dependent artifact updated? If not: create tasks for the uncovered ones. Back tostep 3. 6 YOU APPROVE Product ops approves scope and acceptance changes 7 RESULT Requirement-change impact package
Read the steps as a list
  1. Requirement revised
  2. Trace linked acceptance criteria and artifacts
  3. Create draft updates and owner tasks
  4. Run coverage checks
  5. Is every dependent artifact updated?If not: create tasks for the uncovered ones. Back to step 3.
  6. Product ops approves scope and acceptance changesThe agent waits here for your OK.
  7. Requirement-change impact package

How it decides

It walks traceability links and verifies coverage before closing.

  • Retire only items explicitly made obsolete.
  • Every dependent item must pass a coverage check before closing.
  • Tests that check removed behavior are always flagged.

Make it yours

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

  • Traceability sources (requirements tool, test suite, docs)
  • Owner map per artifact type
  • Deadline for owner updates (default 5 working days)
  • Who approves scope changes

What keeps you in control

It always asks you first

  • Scope changes
  • Test acceptance
  • Release approval

Hard limits

  • Drafts only.

It stops when

  • Done: coverage complete.

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 happensOn 4 September the requirement for report exports drops the XML option. The agent traces 14 linked items and creates 9 owner tasks. After owners respond, the coverage check fails: two automated tests still expect XML. It creates new tasks for the QA owner. The help article is also stale and gets a draft fix. All 14 pass on recheck. Product ops approves.

More agents for qa managers