---
name: scorpio-bug-intake
description: Conduct a focused interview to capture complete bug details and write a structured bug report for downstream investigation.
---

# Bug Intake Interview

Use this skill when the user reports broken behavior and Scorpio is in the bug workflow.

## Goal
Gather complete, high-signal bug details and produce a structured report that unblocks investigation.

## Required Output
Write:
- `{docs.planning}/BUG-REPORT.md`

## Interview Coverage
Collect enough detail to answer:
1. What is happening now?
2. What should happen instead?
3. How can the issue be reproduced step-by-step?
4. How often does it happen?
5. Where does it happen (environment, branch, data set, account)?
6. What is the impact and severity?
7. What logs/errors/screenshots exist?
8. What changed recently that might be related?

## Output Format
Write `{docs.planning}/BUG-REPORT.md` with this structure:

```markdown
# BUG-REPORT

## Summary
- One-paragraph description of the defect and impact.

## Observed Behavior
- ...

## Expected Behavior
- ...

## Reproduction Steps
1. ...
2. ...
3. ...

## Environment
- App/version:
- Branch/commit (if known):
- Runtime/dependencies:
- Data/account preconditions:

## Evidence
- Error messages/log excerpts:
- Screenshots/recordings:
- Related files/paths:

## Severity and Impact
- Severity: Critical | High | Medium | Low
- User impact:
- Business/operational impact:

## Scope and Frequency
- Frequency:
- Affected areas:
- Workaround (if any):

## Suspected Area (Optional)
- Components/files likely involved (if known)

## Open Questions
- Unknowns that must be clarified during investigation

## Done Criteria for Fix
- Clear validation conditions for considering the bug resolved
```

## Guardrails
- Do not implement code changes in this skill.
- Do not assume a root cause without evidence.
- If data is missing, explicitly list gaps under **Open Questions**.

## Session Boundary
After writing the bug report, end the session so Scorpio can continue with `scorpio-bug-investigate`.