shipkit-feedback-buglisted

# 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. --- ## 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 feedback from testing **Workflow position**: - After user testing or beta feedback received - Before debugging/fixing begins - Creates investigated specs ready for implementation --- ## Prerequisites **Required**: - Feedback to process (user provides) **Recommended**: - Stack defined: `.shipkit/stack.json` (tech context) - Codebase indexed: `.shipkit/codebase-index.json` (faster investigation) - Existing specs: `.shipkit/specs/active/*.json` (avoid duplicates) **Schema Reference**: - `references/output-schema.md` - Complete JSON schema definition - `references/example.json` - Realistic bug spec example --- ## Arguments If `$ARGUMENTS` is provided (e.g. `/shipkit-feedback-bug The login button doesn't work on mobile`), treat it as the feedback input. Skip the "paste your feedback" prompt in Step 1 and proceed directly to parsing and categorization. If `$ARGUMENTS` is empty, proceed normally — ask the user to provide feedback first. --- ## Process Overview ``` Step 1: Receive & Parse Feedback ↓ Step 2: Categorize Each Item (bug / feature / won't fix) ↓ Step 3: