QA Test Plan Generator (from code changes)

Given any code change — commit, PR, unstaged file, branch diff, pasted patch, or verbal description — produce a concrete step-by-step manual end-to-end test plan that a human can execute against the running application.

This is for human-driven QA, not for generating automated test code. The output is a checklist of things to click, type, observe, and verify in the actual app.

When to use vs when to skip

• Use when the user wants to know what to test, what could break, or wants a pre-deploy / pre-merge checklist.
• Skip when the user is asking you to write automated tests. Test plans are for humans; automated tests are code.

If unclear, ask once: "Manual test plan to run yourself, or automated tests in code?"

Pipeline

Run these phases in order. Do not skip ahead to writing the plan before understanding the diff.

Phase 1 — Acquire the diff