qa-capturelisted

# QA Capture Log a screenshot as an Asana task in under 30 seconds. No QA pipeline, no review session — just capture and move on. ## Usage ``` /qa-capture /qa-capture "optional extra context for all items" ``` Drop screenshots into `qa/qa-inbox/` in the current project, then invoke. The skill finds them automatically — no path needed. --- ## Steps ### 1. Identify the project Read `CLAUDE.md` in the current directory to get `ASANA_TASK_PREFIX` and `ASANA_PROJECT_NAME`. If not in a project directory, ask: "Which project is this for?" and accept a prefix (e.g. `NORE`, `BSTD`, `KF-WEB`). ### 2. Find screenshots in qa-inbox ```bash ls {PROJECT_ROOT}/qa/qa-inbox/ ``` Filter for image files (`.png`, `.jpg`, `.jpeg`, `.gif`, `.webp`) and files that do NOT already start with a `{PREFIX}-QA-` ref (those are already registered). If no unregistered images found, report "No screenshots in qa/qa-inbox/ to log." and stop. If multiple images found, list them and process each one in turn (one confirmation per image). ### 3. Analyse the screenshot From what you see in the image, determine: - **Title** — a short, specific task title. Describe the symptom, not the cause. Examples: - "Hero image missing on mobile" - "Dashboard gnucash totals show as zero" - "Contact form submit button unresponsive on iOS" - **Severity** — pick one: - `high` — broken functionality, data loss, or visible to clients/end users - `medium` — degraded experience, workaround exists - `low` —