Diagnose Issue

Use this skill to turn incomplete issue input into an evidence-backed problem definition and solution direction. The product is understanding, not an implementation plan.

Operating Rules

• Stay read-only unless the user explicitly asks for edits.
• Verify against the current checkout. Do not trust issue text, Jira fields, stale docs, or a proposed solution without code evidence.
• Separate facts, inferences, and assumptions.
• Prefer high-confidence findings. If evidence is weak, say what is missing.
• Keep solution discussion at the design-direction level. Do not write a step-by-step implementation plan.
• If the reported problem does not exist, say so and cite the evidence.
• If the issue is too vague to investigate, ask the minimum clarifying question needed to start.

Workflow

1. Frame The Intake

Extract the actionable claim from the user's input: