> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/guides/user-story-coverage/use-cases-by-persona/developers.md).

# Developers

The report empowers developers to:

* **Own code quality:** Track coverage progress for user stories, especially those marked critical, ensuring well-tested features are delivered.
* **Collaborate seamlessly with QA:** Share real-time insights, discuss coverage gaps, and work together to achieve comprehensive testing.
* **Facilitate code reviews:** Provide coverage insights during code reviews, helping teammates identify areas that might need additional testing attention.

***

## Tutorials

{% content-ref url="/pages/tWxJNlkeLjX4jkmZpigO" %}
[Code Quality Ownership](/knowledgebase/guides/user-story-coverage/use-cases-by-persona/developers/code-quality-ownership.md)
{% endcontent-ref %}

{% content-ref url="/pages/w6TgFFxix6sHDBCug0m4" %}
[Seamless Collaboration with QA](/knowledgebase/guides/user-story-coverage/use-cases-by-persona/developers/seamless-collaboration-with-qa.md)
{% endcontent-ref %}

{% content-ref url="/pages/x1SOqt3CJxa0uq7xiUGP" %}
[Code Review Facilitator](/knowledgebase/guides/user-story-coverage/use-cases-by-persona/developers/code-review-facilitator.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/guides/user-story-coverage/use-cases-by-persona/developers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.