Draft GitHub issues for the Gumroad codebase. Outputs to an unstaged markdown file in the repo root. Never creates issues on GitHub. Triggers on: "create issue", "write issue", "draft issue", "write a bug report", "file an issue", "create a ticket", or when the user describes a problem or feature they want to turn into a GitHub issue.
Draft well-structured GitHub issues. Output to an unstaged .md file — never post to GitHub.
Gather context from the user. Ask clarifying questions if needed:
If the user points to code, trace the relevant paths to understand the root cause. Include aggregated, anonymized data that quantifies the impact when available (e.g., "99 purchases across 82 sellers are in this state"). Never include PII — no emails, names, IDs, or payment details.
Before writing, assess the scope:
Single issue when:
Parent + sub-issues when:
If suggesting sub-issues, number the solution parts clearly and note which can be done independently vs which depend on each other. Write the parent issue as the full document, then note where to split.
Follow the structure in CONTRIBUTING.md.
Title — Carries most of the weight. Specific and actionable.
## What What needs to change. Be concrete — current vs desired behavior, who is affected, checkbox task list for multiple deliverables.
## Why Why this matters — business rationale or user impact, root cause if it's a bug, links to related issues or prior discussions.
Write to gh-issue-draft.md in the repo root. Do NOT stage or commit.
If the issue should be split into sub-issues, write the parent issue first, then add a ## Sub-issues section at the end listing each sub-issue with a one-line summary. The user can split them manually.
Follow CONTRIBUTING.md for terminology and tone. Additionally:
gh read-only only. Never create issues via CLI.