# Refresh coverage after product change

> Reconcile coverage facets, Cases, benchmark membership, and Snapshots after the target system or its evidence changes.

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
- [Refresh coverage after product change](https://teammately.ai/docs/coverage-engineering/coverage-refresh.md): Reconcile coverage facets, Cases, benchmark membership, and Snapshots after the target system or its evidence changes.
- [The Teammately correctness lifecycle](https://teammately.ai/docs/introduction/correctness-lifecycle.md): Follow specialist AI work from project foundations through coverage, elicitation, construction, evaluation, and improvement.
- [Coverage Gaps](https://teammately.ai/docs/coverage-engineering/coverage-gaps.md): Find missing or underrepresented behavior areas before benchmark evidence becomes misleading.
- [Versioning and Staleness](https://teammately.ai/docs/governance/versioning-and-staleness.md): Know when correctness objects changed and when old evidence may need review.

## Optional
- [Full local context](https://teammately.ai/docs/coverage-engineering/coverage-refresh/llms-full.txt): Complete local context pack for this docs route.