A prompt is a work brief. Specify the task, supply the evidence and define what an acceptable answer looks like. Save the instructions together with an example that passed your review.
A reusable structure
Use this structure: Task: [one outcome]. Audience: [reader and situation]. Source: [approved facts]. Output: [format and length]. Boundaries: [claims or actions to avoid]. Missing information: ask or mark unknown. Acceptance: [checks a reviewer can perform]. Keep source documents separate from your instructions.
Three starting templates
Summary: From the supplied notes, produce decisions, owners and deadlines; mark any missing owner. Reply: Draft a response using only this approved policy; highlight questions the policy cannot answer; do not send it. Content: Turn these confirmed product facts into three different openings for this audience; do not add results or customer claims. Replace placeholders before testing.
Improve the task before adding complexity
Compare the draft to its source. Correct factual errors, vague requests and unsuitable tone separately. One example of a good output can clarify a format better than a long list of adjectives. Use a small collection of normal and difficult inputs to check whether improvements work beyond your first example.
Make your prompt library maintainable
Record its purpose, approved sources, owner, version and date checked. Store a successful output and a failed example. Re-test when the source policy or the selected tool changes. Never assume that a confident answer verifies itself.
Keep this checklist
- Source facts supplied
- Unknowns remain visible
- Draft reviewed before use
- Version and test examples saved
This is an original practical guide. Examples are illustrative; tool interfaces and available features may change.