> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qodo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# View requirement gaps in your findings

> Learn how requirement gaps are generated by the Spec Agent and how they reflect missing or incomplete implementation against linked specifications.

<Badge color="outline-purple" size="sm" shape="pill">Research Preview</Badge>

<Warning>
  Research Preview: The Qodo Spec Agent is set as Research Preview and is under active development. Functionality and results may evolve as we continue to improve the feature. We recommend reviewing and validating outputs before use, and advise against using these features in production or business-critical workflows.
</Warning>

Requirement gaps are findings generated by the Qodo Spec Agent that indicate where a pull request does not fully implement requirements defined in its linked specification.

## How requirement gaps are generated

Requirement gaps are generated by the **Qodo Spec Agent**, which analyzes pull requests that include a linked specification.

The agent compares the implementation in the pull request against the requirements defined in the specification and identifies any discrepancies.

When a requirement is not fully satisfied, the Spec Agent reports a **📎 Requirement gap** finding.

The Spec Agent runs automatically whenever a pull request is opened or updated.

## Prerequisites

1. Log in to the Qodo portal.
2. Set up a documentation integration. For more information, see [Integrate Qodo with Documentation and Design](/install-and-configure/integrations/documentation-and-design-integrations).
3. Navigate to the **Configuration** > **Code review**.
4. Scroll down to the **Advanced** section and enable the **Spec agents** toggle. Changes are saved automatically.

## View the requirement gap in the findings

The Spec Agent adds the following finding type to the review output:

📎 **Requirement gap**: A requirement defined in the specification is not fully implemented in the pull request.

<div style={{ marginBottom: "-1rem" }}>
  <img src="https://mintcdn.com/qodo/-J_3egbdYfsB2m5-/images/code-review/code-review-spec-agent-requirement-gap.png?fit=max&auto=format&n=-J_3egbdYfsB2m5-&q=85&s=9b3274e320956ee98442c46bc49317de" alt="Requirement gap finding in a pull request" width="1840" height="1240" data-path="images/code-review/code-review-spec-agent-requirement-gap.png" />
</div>

Requirement gaps appear alongside other review findings:

* 🐞 Bugs
* 📘 Rule violations
* 📎 Requirement gaps

All findings are displayed in a unified review comment.

## Requirement gap details

Each requirement gap finding includes:

* **Description**: Explanation of what requirement is missing or incomplete
* **Code reference**: Link to the relevant lines in the pull request diff
* **Evidence**: The specification section used for validation
* **Agent prompt**: A suggested prompt to help resolve the issue