draft-issuelisted

# draft-issue Produce a **ready-to-paste issue** (title + Markdown body). This skill NEVER files, creates, or comments on an issue anywhere. No `gh issue create`, no API calls, no browser. Output only — the issue is the user's to file. ## Input (any of) - A bug just found or discussed in the conversation → draft from what was actually observed. - A failing test / log output → use it as the evidence, not as the text. - A plain description from the user → tighten it into the house shape. - Nothing specific → ask what the bug is. Do not invent one. ## The repo outranks this file Before drafting, look for what the project already requires and follow that instead of the defaults below: - **An issue template** — `.github/ISSUE_TEMPLATE/` (pick the one matching bug vs feature), `.github/ISSUE_TEMPLATE.md`, or `.gitlab/issue_templates/`. Fill its sections as written and keep its headings. If it is a **YAML issue form**, answer its fields in order, using each field's label as a heading, and honour the ones it marks required. - **Written rules** — `CONTRIBUTING.md`, `CLAUDE.md`, `AGENTS.md`: title conventions, required labels, a required version or environment block, a reproduction policy. - **What the tracker actually looks like** — `gh issue list --limit 5 --json title,body`. Real practice beats a stale written rule. Where the repo is silent, use the style below. Where it conflicts, the repo wins. Two rules hold either way: **never file anything**, and **never sign the draft a