What problem does it solve? Before a product is built, teams need evidence about what will realistically be attacked and which controls published security knowledge prescribes. This Skill turns a product scope into a structured, schema-validated survey of documented security prior art, with provable coverage records instead of unverifiable claims that "nothing was found". ## Core Features & Use Cases - Threat-vocabulary mapping: Translates product surfaces, data classes, and named dependencies into the terms each security corpus actually indexes (CWE, CAPEC, ATT&CK, OWASP, OSV, KEV, VERIS), with provenance, negative terms, and release stamps. - Angle-based search execution: Runs one of eight search angles (control standards, weakness-to-attack-pattern traversal, incident mining, disclosure mining, package advisories, vendor advisories, supply-chain patterns) producing status-typed coverage cells where failures are recorded as failures, never as zeros. - Evidence-tiered extraction: Deep-reads one source item into a nine-section extraction record with an evidence tier (exploited in the wild, proven exploitable, documented pattern) backed by mandatory tier evidence. - Use Case: Given a scope for a new payments feature, derive the vocabulary map, run the CWE-to-CAPEC angle against the map, and produce a search output whose coverage arithmetic a reviewer can independently verify. ## Quick Start Use security-prior-art-survey to derive a threat-vocabulary map from this product scope and then execute search angle a2 against it.
