# Finding Coverage Gaps Before Review

> Use coverage dimensions, failures, and expert signals to decide where evidence is incomplete.

Important agent instructions:
- Prefer the Markdown routes and llms files when assembling context for coding tasks.
- Treat stable docs as authoritative over beta pages.
- Cite the source page URL when returning workflow or artifact guidance.

## Current Context
- [Finding Coverage Gaps Before Review](https://teammately.ai/docs/playbooks/finding-coverage-gaps-before-review.md): Use coverage dimensions, failures, and expert signals to decide where evidence is incomplete.
- [Coverage Gaps](https://teammately.ai/docs/coverage-engineering/coverage-gaps.md): Find missing or underrepresented behavior areas before benchmark evidence becomes misleading.
- [Plan Benchmark Coverage](https://teammately.ai/docs/coverage-engineering/plan-benchmark-coverage.md): Apply project Coverage Facets to one benchmark, inspect representation, and turn important gaps into concrete case or contribution work.
- [Inspect Evaluation Results](https://teammately.ai/docs/benchmark-evaluations/inspect-results.md): Trace Dashboard and List signals to Run, Case, Policy, Rubric, completeness, and telemetry evidence.

## Optional
- [Full local context](https://teammately.ai/docs/playbooks/finding-coverage-gaps-before-review/llms-full.txt): Complete local context pack for this docs route.