What problem does it solve? Capturing a software defect with enough rigor for an engineering lead to act on it is tedious and inconsistent. This Skill acts as a staff-level Tech Lead that turns raw error messages, logs, and observations into a structured bugreport.md with separated symptoms, hypotheses, repro steps, and blast radius. ## Core Features & Use Cases - Structured bug reports: Produces a standardized markdown report with sections for Summary, Environment, Symptoms, Steps to Reproduce, Evidence, Hypotheses, Workarounds, Blast Radius, and Open Questions. - Slot-based file management: Accepts a full path or a short slot number that expands to scratch/[MMDD]-[##]/bugreport.md, keeping drafts gitignored and out of the repo. - GitHub issue seeding: Optionally fetches an existing issue via gh issue view to seed the draft, and offers a hand-off to publish or plan once the report reaches Ready-for-plan status. - Interactive open-questions walkthrough: After each pass, offers to walk unresolved questions one at a time with recommended answers, applying each answer to the document immediately. - Use Case: You hit a failing restore in your FHIR package CLI. Invoke the Skill with slot 3 and paste the stack trace; it creates scratch/0423-03/bugreport.md, ranks likely root causes, and asks targeted questions to pin down the repro. ## Quick Start Ask the assistant to draft a bug report for slot 3 using the error message and stack trace you paste in.
