# A testable AI build prompt

Fill in one change at a time. Give the same brief to a teammate or a coding assistant.

## Blank brief

**Who and where.** A ___ is trying to ___ on this screen or in this workflow: ___.

**Today.** Starting with ___, they do ___ and see ___.

**Requested change.** When ___, show or produce ___. Include ___ when ___. Preserve the existing ___.

**Small example.** Use these invented records in this exact order: ___. Each record needs these fields: ___.

| Check | Starting records | Action | Exact expected result | Actual result after review |
| --- | --- | --- | --- | --- |
| Ordinary use | ___ | ___ | ___ | ___ |
| A plausible mistake or boundary | ___ | ___ | ___ | ___ |
| Existing behavior to preserve | ___ | ___ | ___ | ___ |

**Handoff.** Make the change in ___. Run each case against the result. Return the observed outputs, any differences, and anything you could not check. Ask about ___ before choosing a default.

## Filled example for a fictional market stall

The packer works from **All orders**. Today it shows every order in intake order. Add a **To pack** view with only orders that are paid and still unpacked, preserving intake order. A view change leaves payment and packing statuses alone. Selecting **All orders** restores the original list.

| Order, in intake order | Payment | Packing |
| --- | --- | --- |
| R4 | Paid | Unpacked |
| R1 | Unpaid | Unpacked |
| R3 | Paid | Packed |
| R2 | Paid | Unpacked |

| Starting records | Action | Exact expected result |
| --- | --- | --- |
| R4, R1, R3, R2 | Select To pack | R4, R2 in that order |
| R1, R3 | Select To pack | No rows. Display “No paid orders need packing.” |
| R4, R1, R3, R2 | Select To pack, then All orders | R4, R1, R3, R2 in that order, with their original statuses |

Independently run these three cases in the changed product. If an unpaid order appears, record its ID and the action that exposed it. A check you cannot run stays open.

## Review a spoken or typed bug note

Practice in a blank note. If you already use Wispr Flow on Mac or Windows, focus the note, hold your push-to-talk shortcut, say the example, then release and wait for the text to appear. Or type it in a text editor without an account or microphone. Review your draft before sending it to a coding assistant.

**Fictional note.** “I picked To pack. I see R four, R one, R two. R one hasn’t been paid. Don’t mark it packed. It should disappear from this view. Keep R four first, then R two.”

| Before you hand it off | Your checked wording |
| --- | --- |
| Exact starting IDs copied from the table, in order | ___ |
| Action and rows actually shown | ___ |
| Both payment and packing conditions, including the negation | ___ |
| Expected rows in order, and what stays unchanged | ___ |

Check your result. Start with R4, R1, R3, R2. Select **To pack**. The first draft shows R4, R1, R2. Only paid orders that are not packed qualify, so the expected rows are R4, R2. Switching views preserves each order’s statuses.

[Wispr Flow’s desktop dictation instructions](https://docs.wisprflow.ai/articles/6409258247-starting-your-first-dictation)

[Run both example drafts in the Creditable Builder Field Guide](https://creditable.vc/guide/testable-ai-build-prompt)
