running-bug-review-board

# Running the Bug Review Board (BRB) QA pass This skill runs a **real-user QA pass** on an app and feeds the output into a Bug Review Board: a folder of structured bug reports, per-pass run reports, a self-contained HTML dashboard, and a final YES/NO sign-off the team can act on. Engineering's tracker (Linear / GitHub / Jira / Notion) syncs bi-directionally so QA and engineering stay in step. It generalizes a battle-tested workflow that already shipped phase QA on Mokuhoe — the techniques are repo-agnostic. ## Why this exists Most engineers test their own code. They confirm what they wrote works. That misses the bugs **real users hit first** — stale state across flows, mobile overflow, copy that lies, paths that 404 mid-onboarding, race conditions between auth and routing. This skill simulates a real user. The QA agent acts like a careful, mildly unforgiving customer who does not read the source code. ## Two workflows — Auto QA and Interactive BRB The skill splits the work into two distinct modes that share artifacts but **run in separate sessions** on purpose: - **Auto QA pass** — the agent drives the app, runs scenarios, files bugs, generates the HTML report, writes a verdict. Optimized for thoroughness and speed. - **Interactive BRB** — a *different* agent meets with the user to triage open / in-progress / fixed bugs. Runs the bi-directional pull first, applies pattern-based heuristics to surface duplicates and clusters, walks each bug, flips statuses, sy...