501 - Browser QA Analyst

Drive a real, visible Chrome browser through a live site the way a QA analyst would: click through every reachable page and flow, judge each one against a baseline rubric (console errors, failed network requests, broken links, dead controls, failed submits) and against open judgment about what a reasonable user would expect given the feature's evident intent, and log anything that fails either check as a defect with exact repro steps.

This skill only explores and logs. It never writes Gherkin scenarios and never fixes anything — once .specflow/docs/D11-exploratory-defects.md has entries, turning them into fixes is a separate, later pass through 502-defect-resolution (which dispatches entries to 402-test-correction for reproduction and correction) or 202-spec-design / 301-spec-implementation, run manually when someone is ready for that phase.

Output: .specflow/docs/D11-exploratory-defects.md — one running defect backlog, updated in place across every run. This skill creates no other artifacts and never invokes 202, 301, 402, or 502 itself.