Cs Issue Report

This is the first stage of a structured issue workflow that turns a user's vague "I found a bug" into a properly documented report. It walks through five mandatory questions,what happened, how to reproduce it, expected vs actual behavior, environment info, and severity,while enforcing a strict rule: capture only observable phenomena, never root cause speculation. That distinction matters because mixing user hunches into the report sends stage 2 analysis down the wrong path. The skill also gates whether an issue takes the fast track (obvious one-liner fix) or standard path (needs deeper investigation). It's opinionated about forcing concrete answers instead of accepting "sometimes it breaks" and refuses to let you skip ahead into diagnosis before the report is locked in.