speckit-bugfix-reportlisted

# Report Bug Capture a bug discovered during implementation and trace it back to the relevant specification artifacts. Produces a structured bug report that maps the issue to spec requirements, plan sections, and tasks. ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). The user describes the bug — what went wrong, error messages, unexpected behavior, or a gap discovered during implementation. ## Prerequisites 1. Verify a spec-kit project exists by checking for `.specify/` directory 2. Locate the current feature's spec directory (by branch name or most recently modified) 3. Verify at least `spec.md` exists ## Outline 1. **Load artifacts**: Read from the current feature directory: - **Required**: `spec.md` (the specification) - **Optional**: `plan.md`, `tasks.md`, `research.md`, `data-model.md` 2. **Analyze the bug**: From the user's description, classify the bug: | Bug Type | Description | Example | |----------|-------------|---------| | Spec gap | Requirement missing from spec | Auth flow doesn't handle expired tokens | | Spec conflict | Two requirements contradict | "Must be stateless" vs "Must track sessions" | | Implementation drift | Code diverges from spec | Spec says REST, code uses GraphQL | | Untested flow | Edge case not covered in success criteria | Concurrent user updates not handled | | Dependency issue | External dependency behaves differently than assumed | API respons