An AI assistant cannot see the work around your question unless you share it. A useful brief makes that context explicit: what you want to accomplish, who the result is for, and what a successful answer should contain.
Start with the outcome
Instead of asking for “some ideas,” describe the next decision you need to make. An outline for a first-time reader and a technical proposal for an engineering team need different levels of detail.
Try a brief like this:
Task: Outline a beginner's guide to our product.
Audience: People who have never used an AI API.
Goal: Help readers understand the first three steps.
Format: Five section headings, each with a short description.
Constraints: Use plain language. Flag missing information.Share a small example
One example of the tone or format you want can remove ambiguity. Use material you have permission to share, and remove personal or confidential details first.
You can also explain what makes the example useful: short paragraphs, clear definitions, or a worked example before the explanation.
Review before you reuse
A well-written response can still contain mistakes. Check factual claims against original sources, test code in an appropriate environment, and make sure the output answers your actual question.
Treat the first response as a working draft. Your review is part of the process.
Keep the parts that work. For the next revision, give specific feedback about what is missing and why it matters.