# 4 · Bugs: reports someone can act on Finding a bug is half the work. The other half is writing it so that someone who wasn't there (a developer, the person, the next agent) can see it happen in a minute and knows how much it matters. A bug nobody can reproduce gets closed as "works for me", and the person who hit it hits it again. --- ### D1 · Write a bug someone else can reproduce **Rule:** Every bug you report has: ``` Title: what goes wrong, where. "Checkout charges delivery at exactly £50" Steps: numbered, from a known start ("Signed in as a test user, empty basket") Expected: what should happen, and where that comes from (the brief, T1) Actual: what happened instead, word for word if there's a message How often: every time, or 3 of 5 tries Environment: browser and version, screen width, device, which build or branch, test account Evidence: a screenshot, the console error, the failing request and its response ``` Write the steps so they work on their own, with the test data spelled out. Leave out anything you guessed about the cause, or label it clearly as a guess. **Why:** The person fixing it starts with only your words. Missing steps, an unknown account or "it broke" means they spend their time recreating your session instead of fixing the bug, or give up and close it. **Agent trap:** "The discount isn't working on checkout, probably a caching issue." No steps, no coupon code, no browser, no expected total. The developer tries a different coupon, sees it work, and closes the report. **Check:** could someone who has never seen this session follow your steps, from the stated start, and see the same thing? If any step relies on something only you know (a record you created, a setting you changed), add it. > **In ihumane Pro** (https://ihumane.ai/#pricing): > - D2 · Rate severity by what it does to a person > - D3 · One bug per report, in the fewest steps > - D4 · Fix what's yours, report what isn't ## Summary checklist - [ ] Every bug has a title, steps from a known start, expected, actual, how often, environment and evidence. - [ ] Every bug has a severity based on its effect on a person, and how many people it reaches. - [ ] One problem per report, with the steps cut down to what still triggers it. - [ ] Bugs in your own work fixed and retested; bugs outside it reported and left alone.