What problem does it solve? Bug reports often arrive ambiguous, and jumping straight to a fix risks solving the wrong problem. This Skill turns a Jira bug ticket or a chat-described misbehavior into a developer-approved investigation document with an evidence-backed verdict, so downstream planning and implementation work from a confirmed diagnosis instead of a guess. ## Core Features & Use Cases - Structured intake and interview: Fetches and distills Jira tickets via the Atlassian MCP, then runs a focused clarifying interview to pin down expected behavior, actual behavior, and a concrete reproduction anchor. - Static evidence-based investigation: Traces the causal path through backend code, builds the platform mental model via the skunexus-docs-c7 skill, and performs git archaeology (log, blame) to distinguish defects from deliberate behavior. - Four explicit verdicts with handoff: Produces one of confirmed bug (with proposed fix and testable acceptance bullets), feature change request, works as designed, or cannot confirm statically, each routed to the right downstream skill after explicit developer approval. - Use Case: A QA engineer files "orders are stuck in status Y" as PHG-456. Say "investigate PHG-456" and the Skill distills the ticket, interviews you, traces the state machine code, and delivers an approved investigation.md with a proposed fix and acceptance criteria ready for the implementation skill. ## Quick Start Ask the AI to investigate PHG-456 and produce an evidence-backed verdict in an investigation document.
