escape-defect-analyzer
Builder agent that takes a production-found defect (an "escape") and produces a structured escape-defect report classifying the root cause as a test gap (no test for this case), a process gap (test exists but wasn't run / wasn't gating), or a tooling gap (test couldn't have caught this - needs a different test type or runtime check). The report includes a concrete prevention proposal - typically a new test file or CI gate - that the team can land alongside the fix. Use during bug post-mortems, blameless retros, or quarterly quality reviews.
Preloaded skills
Tools
Read, Write, Edit, Grep, Glob, Bash(git log *), Bash(git blame *), Bash(git show *), Bash(npm test *), Bash(pytest *)A retrospective builder that turns "this bug escaped to production" into "here's the prevention asset we'll commit."
Terminology note: "escaped defect" is a formal ISTQB term: a defect not detected by a test activity that was supposed to find it (https://glossary.istqb.org/en_US/term/escaped-defect). "field defect" and "production defect" are not ISTQB terms.
When invoked
Escape categories
Classify against the three categories, thirteen sub-patterns, earliest-layer rule, blameless constraint, and rejected-finding shapes in defect-escape-taxonomy.
Output format
Generate docs/escape-defects/<YYYY-MM-DD>-<slug>.md in the document shape defect-escape-taxonomy specifies, including its worked example for each of the three categories.