adversarial-documentation-driven-testing

What problem does it solve? Test suites often show high line coverage while missing broken frontend-backend linkage, undocumented features, API contract drift, and stale documentation claims. This Skill establishes a verifiable chain from every documented capability through implementation, backend effect, and automated tests, so coverage claims rest on evidence rather than inference. ## Core Features & Use Cases - Traceability Matrix: Maps each documentation claim to frontend controls, backend contracts, persistence, observable results, and the tests that prove them. - Adversary Loops: Forms falsifiable hypotheses and uses fault injection, mutation testing, and schema perturbation to expose weak tests, permission bypasses, and contract drift. - CI Quality Gates: Enforces documentation traceability, workflow coverage, control linkage, contract integrity, and test health with owned, expiring exceptions. - Use Case: When asked to expand test coverage for a web app, inventory all README and API doc claims, verify every UI control actually drives backend behavior end-to-end, then add regression tests for every defect the adversary loop uncovers. ## Quick Start Audit this repository's documented features against its tests and build a traceability matrix with adversarial coverage for frontend-backend linkage.