# QA Checklist Agent Runbook

## Project Context To Prepare
- Project goal
- Current repository or workflow context
- Feature scope
- Affected surfaces
- Supported devices
- Known risks

## Input Template
Project:

Goal:

Current context:

Constraints:

Available files, notes, or data:

Expected output:
- QA checklist
- Regression checks
- Device matrix
- Content checks

## Starter Inputs
### First useful run
Use this when you know the goal but still need a structured first draft.

Create QA checks for agent detail exports on desktop and mobile.

Context:
- Current state:
- Constraints:
- Audience:
- Success criteria:

### Project handoff run
Use this when the output will be pasted into a ticket, PR, document, or project brief.

Goal: produce QA checklist for a real project.
Source material:
- 
Constraints:
- 
Review needs:
- Go deep on the risks and constraints listed above.
- Mark assumptions.
- Flag missing context.

### Boundary check
Use this when the request may be under-specified and you want the agent to narrow it safely.

Test an entire product launch with no feature list or supported browser matrix.

Before producing the final answer, identify missing required context and propose a stronger prompt if needed.

## Setup Context Notes
- List changed surfaces, supported devices, known risks, and what must not regress.
- Include the target audience, output destination, and any examples of acceptable or unacceptable work.
- Name what should remain out of scope so the agent does not broaden the task.

## Good Input Example
Feature: install kit export includes RUNBOOK.md and EVALUATION.md.
Affected surfaces: agent detail page, install page, downloaded markdown files.
Devices: desktop and mobile.
Known risks: browser download blocking, stale copy, missing evaluation content.

## Weak Input Example
Make a QA list for the website.

## Weak Input Diagnostics
### Help me with QA Checklist Agent.
- Why it fails: It does not name the project, source material, constraints, audience, or success criteria.
- Stronger input: Create QA checks for agent detail exports on desktop and mobile. Include current context, constraints, expected output, and review criteria.

### Make this better.
- Why it fails: The agent cannot tell whether better means clearer, safer, faster, more complete, or easier to hand off.
- Stronger input: Improve the output for Release QA. Optimize for QA checklist, keep assumptions explicit, and list the changes made.

## Expected Output Shape
- Smoke checks to run first
- Regression checks grouped by affected surface: ID, steps, expected result, pass/fail
- Device and environment matrix against the key checks
- Content checks for copy, translations, links, and data
- Unrequested extras kept to one line each under "If time allows"

## Output Checklist
- Every risk, surface, and environment named in the request has concrete steps and an expected result
- Scriptable checks include the script or command
- Checks are ordered by risk
- Assumptions are marked [ASSUMPTION] and nothing is invented
- Does not state that tests passed or that the release is safe

## Failure Modes
- Checks restate the request instead of giving steps and expected results
- A risk or environment the user named gets no dedicated check
- Expected results are guessed instead of derived from the request
- The checklist claims tests passed or the release is safe

## Handoff Tips
- Paste relevant project files, notes, or constraints before asking for the final output.
- Ask for a first draft, then request a stricter revision using the checklist.
- Keep the generated output with the project ticket, PR, proposal, or team document.