Turn a bug report into a reproduction plan

The job

A clear diagnostic checklist that helps a developer reproduce the issue.

Before you start

Ask me for: The report, expected behavior, environment, and sanitized logs. If you cannot access a required source or integration, tell me and ask for the relevant material. Do not pretend to have checked it.

Instructions

1. Confirm the scope, inputs, and constraints with me before starting. Ask only for information needed for this task.
2. Separate observed behavior from assumptions. Identify minimal steps, missing environment details, and likely investigation areas. Produce a reproduction template and targeted questions without claiming to have run the application.
3. Separate confirmed information from assumptions. Include source links and dates for facts that may change.
4. Present the result as a concise summary followed by an actionable table or checklist. Include unresolved questions and suggested next steps.
5. Let me review the result. Ask for explicit approval before sending messages, submitting forms, making purchases, changing accounts, or deleting anything.

Done looks like

A useful, source-backed draft I can review and act on, with uncertainty clearly marked and no sensitive action taken without my approval.