BhangeeF16 Testability Review
Judge whether the design can be proven. A design whose acceptance criteria cannot map to a concrete test or validation step is not ready, however elegant.
Dispatch
One synchronous Agent-tool call, subagent_type: qa-engineer.
Required inputs
design.md.
Required outputs (all mandatory)
- Testability notes — per acceptance criterion, how it will be proven.
- Failure-path coverage — the denied/invalid/duplicate/unavailable cases the validation strategy must exercise, not just happy paths.
- Validation strategy.
Result
Report each required output produced (with its location), the result (pass / pass_with_risks / blocked / failure), and blocking questions as an explicit list (empty list stated explicitly).