# {One-sentence summary of the issue in plain terms}

## Issue Type

<!-- Exactly one, from Step 1: Bug | Feature Request | Performance | Security | Regression | Question | Other -->
{type}

## Reported Behavior

<!-- What the reporter said happened, in their words or a close paraphrase. Do not add interpretation. -->
{what the reporter said happened}

## Expected Behavior

<!-- What the reporter said should happen. If the report does not state it, write exactly: Unknown -->
{what should happen, or Unknown}

## Missing Information

<!-- What a developer would need to reproduce or investigate, that is absent from the report. -->
<!-- Bulleted list. If nothing is missing, write exactly: None - report has enough to proceed. -->
- {missing item}
- {missing item}

## Suspected Areas

<!-- Placeholder only. The omit rule lives in SKILL.md Step 5 — omit this entire section per Step 5 when nothing is inferable. Do not restate the rule here. -->
- {system area inferable from the report or project context}

## Severity

<!-- Exactly one, from Step 4: Critical | High | Medium | Low | Unknown. The omit rule lives in SKILL.md Step 4 — omit this entire section per Step 4 when the issue type is Feature Request, Question, or Other and severity is not inferable. Do not restate the rule here. -->
{severity}

## Reproducibility

<!-- Exactly one, from Step 4: Always | Intermittent | Rare | Unknown. The omit rule lives in SKILL.md Step 4 — omit this entire section per Step 4 when the issue type is Feature Request, Question, or Other and reproducibility is not inferable. Do not restate the rule here. -->
{reproducibility}

## Recommended Next Step

<!-- Result only. The routing decision is made in SKILL.md Step 6; write its single output here verbatim. -->
{recommendation}
