Skip to main content
Research Preview
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. Review and validate outputs before use, and avoid using these features in production or business-critical workflows.
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.

​
Configure requirement gaps

  1. Log in to the Qodo portal.
  2. Set up a documentation integration under Integrations > Documentation & Design. See Documentation & design integrations.
  3. Navigate to Configurations > Finding types.
  4. Enable the Spec gaps toggle. Changes are saved automatically.

​
Configure requirement gaps in .pr_agent.toml

The portal’s Spec gaps toggle shows as off until you interact with it. Until then, this engine default applies regardless.

​
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.
Requirement gap finding in a pull request
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