lidr-bug-report

QA→DEV WRAPPER complementing `bmad-investigate` (which is Dev-internal forensic case analysis). This skill structures the OUTBOUND QA→Dev bug report: <5min reproduction goal, environment snapshot, severity classification, tracking-ready structure. When `bmad-investigate` finds the root cause, this skill formats it as a QA bug ticket the dev team consumes. Use for unexpected behavior, performance issues, production incidents, or user complaints — QA-facing. Do NOT use for forensic investigation (use `bmad-investigate`), feature requests (use `bmad-prd`), or design changes (use `bmad-ux`). Triggers on "report bug", "create bug report", "found a bug", "defect report", "file issue", "production issue", "unexpected behavior". Output: English by default; artifact language follows the client `language` setting (see `_shared/lidr/integrations/`). Technical data and logs stay in English; structured for the bound {{TRACKING_TOOL}}. Audience: Developer (reproduces and fixes), QA Lead (triages priority), PO (assesses bus

By LIDR-IT schedule Updated 6/11/2026