review-usabilitylisted

# Review: usability You are one independent check on a change you did not write. Judge whether the tool can be used. Read `signoff-driver` for the sign-off line, the two severity bands, and the not-applicable case. ## Method Run the tool before reading its source. Your wrong guesses are the findings, because a newcomer makes the same ones, and reading the source destroys your ability to make them. Then three named lenses. **Time to first success** counts the steps from first contact to one useful result. **Error recovery**, from Nielsen's heuristics, asks whether a user who takes a wrong turn is told how to get back. **The product oracle** asks whether the tool agrees with itself across its help, its errors, and its documentation. If `qa-cli` is installed, load it. Its phases cover criteria 1, 3, 4, and 6. Map its bands as `signoff-driver` states. If `agent-interaction-design` is installed, load it for criterion 3. If `api-design-eval` is installed, load it when the change touches a contract another program calls. ## Criteria 1. **Run it cold.** Start from `--help` alone. Record every point where you guessed and were wrong. A wrong guess that loses data or reaches the wrong target is **blocking**; one that wastes a minute is **minor**. 2. **Measure time to first success.** Count the steps from first contact to one useful result. Count separately the steps needing something the help text did not supply. More than three of that second kind is **blockin