shipkit-feedback-bug

# shipkit-feedback-bug - Feedback to Investigated Bug Specs **Purpose**: Transform raw user feedback into fully investigated bug specifications with root cause analysis, blast radius assessment, and captured learnings. **Protocol:** This skill follows the canonical elicitation protocol defined in `install/shared/references/elicitation-protocol.md` (the *mechanics* — marker, state files, resume). The fork-safe path below is this skill's specific application of that protocol. **Calibration:** Apply `install/shared/references/ground-or-ask-calibration.md` (the *intelligence* — propose vs ask). **Ground first:** the feedback text, the codebase, and `stack.json` are the cited signals. Propose the bug spec (repro steps, root cause hypothesis, severity) grounded in those signals, tagged with source; flag low-leverage guesses as `guessed`. **HIGH-LEVERAGE fields to ask** when ungrounded: reproduction steps or expected-vs-actual behavior the codebase cannot disambiguate; severity when the classification would change prioritization. Ask those rather than guessing. **Low-leverage detail** (reporter name, ancillary environment metadata that the stack implies) → propose a flagged default, no pause. **Never** silently invent an ungrounded root cause or reproduction the investigation cannot support. --- ## When to Invoke **User triggers**: - "Triage this feedback" - "Process these bug reports" - "I got user testing feedback" - "Here's what testers found" - User pastes a dump of feedba...