Use when a defect has been confirmed in production and the team must name which class of gap let it through before deciding what to build. Classifies it as a test, process or tooling gap and one of thirteen sub-patterns at the earliest layer that should have caught it, with the fix, without blame.
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
The owner of this plugin can generate scenarios and run an eval with the Tessl CLI.
tessl scenario generatetessl eval run