Write a Reusable Prompt Brief

An original ToolNav workflow. Examples are illustrative planning scenarios.

Deliverable

Specify a memo, description or email and the decision it supports. Three headlines for a named landing page have a concrete stopping point; improving marketing does not. Add the intended reader and publication context.

Source material

Supply approved facts and clearly label unknown claims. Ask the assistant to flag missing evidence rather than invent statistics. Keep instructions separate from quotations so source material cannot silently become a new task command.

Constraints

Set length, tone, required sections and prohibited claims. For directory copy, prohibit invented users, unsupported rankings and unverified prices. Specify the destination link and whether the draft should include unresolved questions after the final text.

Complete example

Example: write a 100-word English description using only a supplied feature list; address small teams; include input, output and a limitation; end with a demo link. Replace the list with actual product facts before publishing.

Controlled revision

Identify missing context, weak evidence, structure or tone as the failure. Change the relevant brief section and compare against the same rubric. Rewriting everything at once hides what helped and encourages endless tuning without a usable draft.

Save a tested template

Store the brief beside a successful output and review notes. Remove confidential examples before sharing. Try a bounded task in Claude, then apply the product copy checklist before publishing.

Acceptance checklist

Before approval, check the intended audience, factual claims, permissions, final output and destination. Assign a reviewer and log unresolved questions. Review the exact file or page that users receive rather than only a preview. Keep assumptions separate from observed results so a later review can understand the limits.

Version and follow-up

Save the brief, approved output and review notes under a clear version. Keep rejected drafts separate. When requirements change, update the source and repeat affected checks. Browse ToolNav around a real task and compare current provider terms before adopting a new tool; feature names alone do not establish workflow fit.