01 / START HERE
A useful way to approach it.
A reusable instruction defines inputs, work, boundaries, and output. For a recurring client update, structure and review rules can remain stable while the status changes. Treat the template as a specification you can inspect and revise.
Keep the template as text and paste it into the relevant chat. No general saved-instructions setting, persistence, or scheduled run is assumed. The fictional cases below illustrate expected review behavior; they are authored examples, not measured live AI results.
02 / THE PROCESS
Go from question to next step.
- 01
Choose a repeatable drafting job
Pick one task with a recognizable input and output, such as a meeting recap, client update, or research comparison. Describe what a good result helps you do. Avoid a universal instruction attempting to govern every future conversation. A narrow job is easier to evaluate and revise when an output misses the mark.
- 02
Name required and optional inputs
Use readable placeholders such as {{audience}}, {{facts}}, and {{unresolved_items}}. Explain what belongs in each field and whether it can be empty. Keep secrets and unnecessary sensitive information out of reusable examples. A placeholder is a reminder to supply context; it does not fetch that information or establish permission to use another app.
- 03
Write stable boundaries and output rules
Specify the required sections, useful length, tone, and handling of uncertainty. Tell the assistant what to do when an input is missing: ask a question or mark the gap. State that facts and commitments must come from supplied material. Do not rely on a generic instruction to 'be accurate' to define your actual review criteria.
- 04
Try contrasting authored cases
Prepare an ordinary input, an incomplete input, and an input with conflicting statements. Inspect whether the resulting draft would preserve uncertainty, request clarification, and follow the format. If you run the prompt in a workspace, judge the actual output; do not treat an illustrative table as evidence that the template has already been validated there.
- 05
Revise and keep a version note
Change the instruction addressing the failure you observed rather than adding a long list of unrelated rules. Retain a short note describing what changed and which case you will check again. Keep human review in the workflow. A reusable prompt reduces repeated briefing, but it does not guarantee consistent answers or authorize actions on your behalf.
03 / YOUR STARTING POINT
A prompt you can make your own.
Replace the bracketed fields. Add only information you have permission to share. This is a reusable text prompt; it does not run a task from this page.
Draft a client update from {{confirmed_facts}} for {{audience}}. Context: {{project_context}}. Unresolved items: {{unknowns}}. Use sections: current position, completed work, blocker, and requested next action. Preserve supplied dates and commitments; do not invent progress or approval. If a required fact is missing or inputs conflict, flag it before drafting that section. Keep the update under {{word_limit}} words. After the draft show a fact-check list. Produce text for my review only; do not imply it was sent, scheduled, or saved elsewhere.04 / SEE THE SHAPE OF IT
Illustrative instruction test cases
Authored fictional inputs and expected review behavior; these cases are examples, not live AI executions or a reliability benchmark.
| Input case | Desired behavior | What to inspect |
|---|---|---|
| Complete status notes | Draft the requested update sections | Every fact comes from the notes |
| No review date supplied | Flag the missing date | No invented calendar commitment |
| Two conflicting approval statements | Ask which statement is current | Do not silently choose one |
| Placeholder left unfilled | Identify missing input | Do not publish placeholder text as fact |
A good template includes failure behavior. Keeping the same output format is less useful if the instruction silently invents the information needed to fill it.
05 / KEEP YOUR JUDGMENT
What to watch before you use it.
Making the template too general
Broad personality instructions cannot replace task-specific inputs and acceptance checks. Start with one repeatable job.
Confusing placeholders with connections
A field such as {{calendar}} means you must supply relevant information. It does not imply access to a connected calendar or permission to act.
Adding rules without testing them
Every new rule should solve a recognizable problem. Check the affected case again instead of assuming a longer prompt is more reliable.
06 / THE FINAL PASS
A little review goes a long way.
Your checks stay on this page. They do not approve or run a task.
07 / GOOD QUESTIONS
Before you begin.
Will these instructions apply automatically in later chats?
This guide creates a portable text template. Paste it where you want to use it and provide the current inputs. Do not assume general persistence, a saved-instructions setting, or a scheduled run from the template alone.
How many rules should the instruction contain?
Enough to define the job, inputs, boundaries, format, and review conditions. Add a rule when it addresses a real ambiguity or observed failure. Remove redundant wording that makes the important instructions harder to follow.
Can a reusable prompt eliminate review?
No. Inputs change and answers can be mistaken. Use the template to make output easier to check, then verify facts, unresolved conditions, and any proposed action before relying on or sharing the result.