issuelisted

# /issue - GitHub Issue Generation ## Input Treat `$ARGUMENTS` as the issue description. When it is empty, ask for the description via AskUserQuestion. When only an issue number or URL arrives, transfer a plan into that filed issue. Take the body via `gh issue view <ref> --json title,body` and start at Phase 2's duplication match. Leave the existing body unchanged except where the plan transfer requires it. Without a plan draft, suggest running `/think` and stop. An issue that already carries a `## Plan` section goes to `/qualify` for inspection instead. ## Language Read `language` from `~/.claude/settings.json` and generate the issue body in that language. Translate the template's body into it as well. Default to English when it is unset. Headings that come from the template stay in English. ## Phase 1: Drafting 1. Read `.claude/OUTCOME.md`, and generate the stub via `/outcome` when it is absent. Confirm the issue sits inside the outcome state. When it sits outside, ask via AskUserQuestion whether to redefine the non-goal or split it off as its own task 2. Detect the type from the description 3. For a bug, judge whether it is minor, and offer fixing it with `/fix` instead of filing when it is 4. For a feature or a bug whose Why the description does not carry, pin the Why down per ${CLAUDE_SKILL_DIR}/references/why-wall-bouncing.md 5. List the criteria from the description and what step 4 settled, and ask about splitting when two or more are independently implementable