bmad-review-edge-case-hunter

Exhaustive path enumeration analyzes full files or specific diffs by walking all branches and boundary conditions, reporting only paths lacking explicit guards. It targets unhandled scenarios while ignoring already-handled paths.

Exhaustive path tracing is a deterministic traversal method that walks all branching paths in code or specs to reveal gaps. It focuses strictly on boundary conditions to identify unguarded edge cases for robust discovery.

Yes, you can audit specification boundary conditions by enumerating all possible execution paths. The analysis reports only unhandled scenarios, listing gaps where explicit guard conditions are missing.

Edge-case path analysis works for both full files and specific diffs. It requires deterministic path traversal across the targeted content to identify boundary conditions lacking explicit guards.

The best way to identify unguarded execution paths is using a method-driven, exhaustive analysis rather than an adversarial approach. It deterministically traverses paths to report only scenarios lacking explicit guards.

You should not use exhaustive edge-case path enumeration when you need adversarial review or attitude-driven critique, as this method is strictly orthogonal and focuses only on deterministic boundary condition discovery.