Front page / By role / Write the test plan

Write the test plan

Decide scope, depth and schedule based on risk.

For QA or test engineer · Knowledge pack

What are you planning?

One line is enough. Step 1 asks the rest in your AI app, and nothing is done until you approve the brief it writes.

In the case folder's materials/: The tasks, dates, people and constraints you already have, in any form.

One planner, every constraint checked by code. Not found and out of scope are valid answers here: it says so instead of guessing.

How the field does this well: Write the check first: a failing test, a typecheck or a command that comes back pass or fail.
Work one unit at a time and show the command that ran and its output as evidence.
Have a reader who did not write the change review it against the written spec, and skip style.
Keep state in files: a list of checks whose status may only flip to passing, and a progress note.
Ground it first: Ask for, or look in materials/ for: the repository or files to change, how its tests run, and the coding standards. If there is none, say plainly that the result rests on general defaults, and name them.
What stays with the person: Scoping ambiguous work, architecture choices, and the final merge or release. Prepare these; never decide them.
The check that makes it trustworthy: A failing check written first, a passing run shown as output, and an independent review of the change against the spec.
The person's own data: If the person has connected GitHub, Linear, Jira + Confluence, Postgres, read their data through that connector instead of asking for exports, and say which source each number or fact came from. Without one, work from materials/.

On your computer: Your files in materials/, every result in outputs/, the work itself. It runs in your AI app, on the plan you already pay for.
With Cheatcode: The steps, the gates and how far each case has come, so a case survives closing the app. See your cases.