Library / Working with a coding agent / Repro steps
No. 089·noun·also called reproduction steps, steps to reproduce, STR

Repro steps

The exact steps that make a bug happen, so someone else can see it for themselves and fix it.

SPECIMEN · DIAGRAM · SEQUENCE
You
App
1open a project2add task with emoji3click Save4spinner forever (bug)
Definition

What it is

Repro steps (steps to reproduce) are a numbered list of exactly what to do to trigger a bug, followed by what you expected and what actually happened.

A bug that can be reproduced can usually be fixed quickly. A bug described as "sometimes it doesn't work" can take ages, because the builder has to guess.

Include where it happened (page, device, browser), any specific data involved, and screenshots or error messages.

Say it like a builder

How to ask for it

Vague

“Sometimes saving doesn't work.”

Precise

“Repro steps: 1. Open any project. 2. Add a task with an emoji in the title. 3. Click Save. Expected: task saves. Actual: spinner forever, console shows "invalid character". Chrome on Mac, production. Tasks without emoji save fine.”

Why it works

"Sometimes" gives nothing to chase; repro steps with expected vs actual let the builder trigger and fix it immediately.

In the wild

You've seen this in

  • GGitHub issue templates
  • SSupport tickets that get fixed fast
  • QQA bug reports
Usage note

Often confused with

BugThe bug is the problem; repro steps are how you describe it so it can be fixed.Acceptance criteriaAcceptance criteria define done for new work; repro steps describe a failure in existing work.