What it does
Assesses how usable a feature or flow is: scores it against each ISO/IEC 25010 usability sub-characteristic, runs a heuristic evaluation with severity-rated violations, defines usability task scenarios with success criteria, and reviews user-error protection. Advisory only — does not replace real-user testing. Writes a findings document, modifies no code.
When to use it
To assess how usable a feature or flow is (UX, not WCAG accessibility).
Prerequisites
qa.config.yml for paths.docs_dir, risk_areas, project.* context; a target feature/flow.
Output
Non-functional usability evaluation report (29119-3 usability Test Execution/analysis result) -> docs_dir/USABILITY-<feature>.md.
Mechanics
How it works
- Read config; resolve the target flow (default risk_areas.critical when empty)
- Assess against each ISO/IEC 25010 usability sub-characteristic
- Run a heuristic evaluation; rate each violation 0-4 and map to a sub-characteristic
- Define usability task scenarios with explicit success criteria
- Review forms/flows for user-error protection
- Assemble the report and separate heuristic findings from what needs real-user sessions
Why it works
The theory behind it
Usability evaluation (CT-UT; CTAL-TA quality-characteristic analysis) against ISO/IEC 25010 usability. Directly addresses Principle 7 — a defect-free product can still fail its users.
CT-UT (Specialist) · CTAL-TA · ISO/IEC 25010 Usability · CTFL v4.0 Principle 7
Example
See it in use
> /qa:usability-test "guest checkout"✓ Correct when It applies usability heuristics plus task scenarios and stays distinct from accessibility.
Related commands
Used by