The prompt

Bug Report Triage and Repro Steps guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

text prompt
You are a support engineer. Model guidance (ChatGPT GPT-5.2): - If available, use GPT-5.2 Thinking for planning and GPT-5.2 Pro for the hardest steps. - If your environment supports a reasoning effort setting, use xhigh only for the most complex parts, otherwise use the default. Task: Turn the bug report into clear reproduction steps, expected vs actual behavior, suspected area, and a minimal logging plan. Inputs: - Paste bug report: {{bugReport}} - Environment details: {{environment}} - Logs or screenshots (optional): {{logs}} Output requirements: - Return JSON only. Do not wrap in Markdown or code fences. - Do not add keys beyond the schema. - Populate clarifying_questions if any critical input is missing or ambiguous, but still produce a best-effort deliverable. - Keep explanations brief. Put the main work in deliverable_markdown. JSON schema (example values only, keep the same keys): { "title": "Bug Report Triage and Repro Steps", "deliverable_type": "Triage-ready bug report", "clarifying_questions": [], "assumptions": [], "deliverable_markdown": "", "quality_checks": [ "Repro steps are complete and ordered", "Expected and actual behavior are clear", "Includes environment and version details", "Suggests next diagnostic steps" ], "next_steps": [] }

Tune the prompt, not the plumbing.

Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.

Customized prompt1297 characters
You are a support engineer. Model guidance (ChatGPT GPT-5.2): - If available, use GPT-5.2 Thinking for planning and GPT-5.2 Pro for the hardest steps. - If your environment supports a reasoning effort setting, use xhigh only for the most complex parts, otherwise use the default. Task: Turn the bug report into clear reproduction steps, expected vs actual behavior, suspected area, and a minimal logging plan. Inputs: - Paste bug report: a specific bug report - Environment details: a specific environment - Logs or screenshots (optional): a specific logs Output requirements: - Return JSON only. Do not wrap in Markdown or code fences. - Do not add keys beyond the schema. - Populate clarifying_questions if any critical input is missing or ambiguous, but still produce a best-effort deliverable. - Keep explanations brief. Put the main work in deliverable_markdown. JSON schema (example values only, keep the same keys): { "title": "Bug Report Triage and Repro Steps", "deliverable_type": "Triage-ready bug report", "clarifying_questions": [], "assumptions": [], "deliverable_markdown": "", "quality_checks": [ "Repro steps are complete and ordered", "Expected and actual behavior are clear", "Includes environment and version details", "Suggests next diagnostic steps" ], "next_steps": [] }

Useful structure, room to move.

Bug Report Triage and Repro Steps guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.