issuelisted

# Issue — QA Issue Reporter Registers a new QA issue for the current project. Assigns a reference number, writes a structured file to `qa/qa-inbox/`, and appends to `qa/qa-log.md`. Does not fix anything — just intake and registration. Use `/qa` to work through issues once they are registered. --- ## Invoke ``` /issue /issue broken contact form on mobile ``` If a description is passed inline, use it. Otherwise, ask. --- ## Steps ### 1. Scaffold check Confirm `qa/` exists in the current project root. If not, stop and tell Mark to run `/qa` first to set up the QA structure. ### 2. Gather the issue details If invoked with an inline description, use that as the starting point. Ask for any missing fields using `AskUserQuestion`: **Required:** - **Description** — one line, plain English: what is broken or wrong - **Severity** — `critical` / `high` / `medium` / `low` - **Feature area** — what part of the site (e.g. "contact form", "mobile nav", "checkout", "homepage hero") - **Type** — `description` (text only) / `image` (screenshot exists) / `bundle` (multiple files) **Optional:** - **Steps to reproduce** — if the issue is not obvious from the description - **Expected behaviour** — what should happen - **Actual behaviour** — what actually happens - **Notes** — any extra context If an inline description was provided, ask only for the fields that are still missing (severity and feature area at minimum). ### 3. Assign the reference number Read `qa/qa-counter.json`: ``