# Technical content brief and topic worksheet

Define a reader task and a verifiable answer. Examples are fictional; missing evidence stays missing.

## Topic selection

| Reader task | Source and date | Consequence | Existing answer | Material we can demonstrate | Effort/reviewer | Decide: brief, investigate, or defer |
|---|---|---|---|---|---|---|
| Fill in | Fill in | Fill in | Fill in | Fill in | Fill in | Fill in |

Fictional candidate: diagnose duplicate webhook deliveries without repeating an order write. A working synthetic example and recurring implementation questions support a brief. An unsupported integration requires a compatibility decision rather than a tutorial promise.

## Production brief

- Owner and reviewer:
- Reader, context, and starting knowledge:
- Task and expected output:
- Format: tutorial, reference, troubleshooting, comparison, or another justified format:
- Scope and boundaries:
- Primary sources and approved input material:
- Supported environment and relevant versions:
- Sample inputs and whether they are synthetic:
- Steps, expected output, and failure cases:
- Starting-point test and reviewer result:
- Known limitations:
- Relevant next action:
- Distribution route and prerequisites:
- Complete production/review capacity:
- Maintenance owner and review trigger:

## Acceptance and outcome

- Does the piece deliver the stated task?
- Can a reviewer reproduce it from the documented starting point?
- Are product claims supported and current?
- Are confidential details removed or approved?
- Does the next action fit the reader's task?
- What evidence will show relevant use?
- Questions or failures found after release:
- Next correction or topic decision:


---
Original resource by Jon Bishop. CC BY 4.0. Illustrative examples are not customer results.