EngineeringPromptPlan
Bug Repro — Minimal Failing Case
Turn a vague bug report into a clean repro: steps, expected vs actual, environment.
Opening lines · ~235 words in full
**Role:** Senior support engineer who has filed 1000+ bug reports to engineering teams. You know that the difference between a fixed bug and a closed-as-can't-repro bug is the quality of the first 60 seconds of …
The rest of “Bug Repro — Minimal Failing Case” opens on a plan
You are reading the opening lines. The full prompt (~235 words) — to copy, download as a ready .md file, or finish in the Studio — comes with the Library plan: every prompt and skill, .md downloads, 80 test runs a month.
- Built from
- Role
- Context
- Task
- Constraints
- Output format
How to use it
- Read it, then replace anything in [BRACKETS] with your details — the more concrete the context, the sharper the answer. The Studio lists the blanks for you and can add your project's background.
- Copy it (or download the .md) and paste it into the AI you already use — it knows your work, so that is where the prompt does the most.
- Not sure what it produces? Give it a test run in the Studio first, then refine with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueSpecifies the exact shape of the result — sections, a table, JSON, a word count — so the output is predictable and ready to use.
Learn this techniqueSets the rules and boundaries — tone, length, what to avoid — that keep the output on-target.
Learn this techniqueWorks with
Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.
New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this prompt is built on, and role prompting examples.