{
  "schema_version": 2,
  "kind": "shortening-method",
  "format": "agent-skill",
  "id": "reproduction-steps",
  "name": "Reproduction steps",
  "category": "Technical",
  "summary": "Extract the shortest supplied procedure that still demonstrates a defect.",
  "use_cases": [
    "Issue reproduction",
    "QA handoffs"
  ],
  "word_count": 153,
  "url": "https://sho.rten.it/methods/reproduction-steps/",
  "instructions_url": "https://sho.rten.it/methods/reproduction-steps/SKILL.md",
  "skill_url": "https://sho.rten.it/methods/reproduction-steps/SKILL.md",
  "json_url": "https://sho.rten.it/methods/reproduction-steps/llms.txt",
  "plain_text_url": "https://sho.rten.it/methods/reproduction-steps/prompt.txt",
  "license": "MIT",
  "sources_url": "https://sho.rten.it/sources/#reproduction-steps",
  "skill_name": "reproduction-steps",
  "skill_description": "Extract the shortest supplied procedure that still demonstrates a defect. Use for Issue reproduction, QA handoffs.",
  "agents_md_url": "https://sho.rten.it/methods/reproduction-steps/AGENTS.md",
  "sources": [],
  "instructions": "Turn the supplied troubleshooting narrative into a minimal reproducible procedure. Select this when the reader needs to make a reported failure happen, rather than triage the full issue.\n\nSeparate required setup from ordered actions. Keep state, permissions, versions, input values, timing, and reset instructions when they affect reproduction. Remove unsuccessful detours and repeated actions unless repetition is itself the trigger. Do not remove a step merely because it looks unnecessary; mark uncertain prerequisites as uncertain when the source does.\n\nEnd with the observed result and the expected result. Preserve supplied frequency and a control case if it narrows the failure. Quote exact commands, selectors, filenames, and error text. Never substitute an untested shortcut or imply that you ran the procedure.\n\nOutput Setup, numbered Steps, and Result. Add Expected and Scope when supplied. Do not add missing setup or diagnostic actions; identify a missing step only when it prevents the procedure from being followed.",
  "example": {
    "context": "Concurrent editor state",
    "before": "I can reproduce this in Board 2.6 using an Editor account with an existing board. Open the board in two tabs of Chrome 126. In the first tab rename the board to Sprint A and save it. Leave the second tab open without refreshing it. In that second tab add a card named Review and save it. The board name then changes back to its original name. I expected the name Sprint A to remain. I repeated these actions twice and it happened both times. Refreshing the second tab before adding the card prevents the name change. I also checked the browser console, but it contained no errors.",
    "after": "Setup: Board 2.6; Chrome 126; Editor account; existing board.\nSteps:\n1. Open the board in two tabs.\n2. In tab 1, rename it Sprint A and save.\n3. Without refreshing tab 2, add a card named Review and save.\nResult: The original board name returns (2/2 attempts).\nExpected: Sprint A remains.\nScope: Refreshing tab 2 before step 3 prevents the failure.",
    "must_preserve": [
      "Board 2.6; Chrome 126; Editor account; existing board",
      "Two tabs; rename Sprint A then add Review without refreshing second tab",
      "Original name returns; expected Sprint A",
      "2/2 attempts",
      "Refreshing tab 2 before adding card prevents failure"
    ],
    "omitted": [
      "The console had no errors; it does not change the reproduction procedure"
    ],
    "kind": "illustrative"
  }
}