A prompt asks the model to invent missing business facts. The useful response is a targeted correction with an observable acceptance check. That keeps the repair tied to the problem instead of turning it into an open-ended redesign.
Find the likely cause
The task requires details that were never supplied.
Treat this as an explanation to verify against the actual work. Look at the input, the relevant decision, and the final result together. If the evidence does not support this diagnosis, investigate the mismatch before applying a convenient but unrelated fix.
Make the targeted correction
Require explicit unknowns and route missing facts to the owner.
A good prompt brief specifies the task, audience, source material, constraints, and acceptance criteria before requesting prose.
Check that the repair worked
Inspect every name, price, date, and capability in the output.
Repeat the check on the final version that the reader or customer will encounter. An approved draft, a preview, and a published result can differ; the acceptance decision should concern the version people actually use.
Prevent the next related failure
A separate issue to watch for is this: the output format changes between runs. Provide a clear structure and validate required fields.
Monitor the useful outcome
Track first-review acceptance and the types of correction required across repeated tasks.
Keep a short record of the original symptom, the evidence behind the diagnosis, and the result of the acceptance check. That record makes the solution reusable when the same condition appears again, without assuming that every superficially similar problem has the same cause.