What problem does it solve? Engineers facing production failures, data-consistency risks, or poorly tested legacy code often lack structured diagnostic questions. This Skill supplies focused, book-inspired reference checklists that surface the right questions for reliability reviews, schema changes, API authorization, SQL diagnosis, debugging, and test design without imposing mandatory workflows. ## Core Features & Use Cases - Targeted reference selection: Read only the reference matching the actual risk, such as Release It! for retry/timeout/overload design, Designing Data-Intensive Applications for transactional or derived-data changes, or Working Effectively with Legacy Code for safe test seams. - Broad engineering coverage: Includes contract boundaries, release dependencies, API authorization, SQL diagnosis, telemetry evidence, debugging, test design, interface design, domain modeling, threat modeling, recovery planning, retrieval contracts, knowledge bundles, and developer first-value reviews. - Scope and authority guardrails: References are diagnostic questions, not mandates; reviews are read-only unless edits are authorized, and no deployments, migrations, or new services are granted. - Use Case: When modifying an endpoint that writes across tenants, consult the API authorization reference to check caller/tenant/object enforcement and add denied-write tests before shipping. ## Quick Start Ask the agent to review your planned retry and timeout changes using the engineering references for reliability risks.
