Report Bug

File a structured Bug issue from a QA finding. Core value: the Gherkin scenario that failed becomes the reproducible test evidence, and the originating Task and Feature are linked automatically so nothing loses its context.

Fast path (for wtf.hotfix)

When invoked from wtf.hotfix, skip the Gherkin-derivation and Ubiquitous-Language mapping work — the goal is to file the issue fast so the fix can start. Run only:

• Step 0 — GitHub CLI setup (skip if already confirmed this session).
• Step 1 — Identify the source (one-sentence bug, impact, optional task link).
• Step 3 — Gather bug details, but only a. Observed behavior, b. Expected behavior, and c. Reproduction steps. Skip contract violation / regression risk / suggested fix questions — the hotfix will uncover those.
• Step 6 — Draft the Bug report with only the sections the fast path produced (leave Contracts Violated, Regression Risk, Suggested Fix blank or marked "Fast path — to be captured during hotfix").
• Step 7 — Review briefly (or skip if the caller signalled non-interactive).
• Step 8 — Create the issue.

Return the bug issue number to the caller. Do not run the offer-next-steps prompt in step 9.

Process