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

# Technical Q&A

> Answer engineering questions from your codebase docs and past decisions.

Engineers lose hours asking around for how a system works or why it was built that way. Hops answers from your architecture docs, ADRs, READMEs and past threads, with a source for every claim.

<Info>
  **How it runs:** Ask Hops. No skill or automation needed. Connect your apps and ask in any chat.
</Info>

## What it does

* **Answers from your own docs.** Hops reads GitHub code and READMEs, ADRs in Notion or Google Docs, and past Slack threads.
* **Leads with the answer, then cites sources.** Every point links to the file, ADR or thread it came from.
* **Flags drift.** When the docs disagree with the code, Hops says so and shows both.
* **Says when nothing is documented.** Hops tells you the answer is not written down and suggests who has worked on it.
* **Respects access.** Hops only reads what each connection can see.

<Frame>
  <img src="https://mintcdn.com/hopsdocs/E03FYifT87c9QmFJ/images/use-cases/pe-technical-qa.gif?s=d4253116b2d09b8ef48e420dfeaa5386" alt="tech-qa skill, Hops answered an engineering question from ADRs and READMEs" width="1440" height="810" data-path="images/use-cases/pe-technical-qa.gif" />
</Frame>

## Ask Hops

Copy a prompt into any chat with Hops, or mention `@Hops` in a Space.

```text theme={null}
Why do we retry webhooks the way we do? Cite the ADR.
```

```text theme={null}
Which service owns the dead-letter queue for Acme's webhook deliveries?
```

```text theme={null}
How does auth token refresh work in the mobile API? Link the code and docs.
```

```text theme={null}
Is our README for the billing service still accurate? Compare it with the code.
```

```text theme={null}
What did we decide in past threads about moving off the monolith?
```

Example reply:

> Webhooks retry with exponential backoff, 5 attempts over 24 hours (ADR-017).
>
> * After the last attempt, the event moves to the dead-letter queue.
> * The platform team owns the queue and replays events on request.
> * The README says 3 attempts, but the code uses 5. The README is out of date.

## What you get

* **An answer in chat**, in the same thread, with a linked source for every point.
* **A saved Doc, when you ask for one.** Say "save this as a doc" and Hops writes the answer to **Docs** in the Space.

## Connections needed

Connect these apps. Each card opens Connections in the app.

<CardGroup cols={3}>
  <Card title="GitHub" icon="github" href="https://app.hops.ai/my-hops/connections">
    Code, READMEs and pull requests.
  </Card>

  <Card title="Notion" icon="book" href="https://app.hops.ai/my-hops/connections">
    ADRs and architecture pages.
  </Card>

  <Card title="Google Docs" icon="file-lines" href="https://app.hops.ai/my-hops/connections">
    ADRs and design docs.
  </Card>

  <Card title="Slack" icon="slack" href="https://app.hops.ai/my-hops/connections">
    Past engineering threads.
  </Card>
</CardGroup>

## Set it up

<Steps>
  <Step title="Connect your apps">
    Connect the apps above in **Connections**. Use Notion or Google Docs, whichever holds your ADRs.

    See [Connections](/docs/connections/overview).
  </Step>

  <Step title="Pin what matters (optional)">
    Create a **product-eng** Space and pin your architecture overview and ADR index in Space context, so Hops checks them first.

    See [Spaces](/docs/spaces/overview) and [Space context](/docs/spaces/space-context).
  </Step>

  <Step title="Ask">
    Ask Hops an engineering question in chat. That's it.
  </Step>
</Steps>


## Related topics

- [Product & Engineering](/teams/product-engineering.md)
- [Policy Q&A](/teams/hr-people-ops/use-cases/policy-qa.md)
- [Interview debrief](/teams/hr-people-ops/use-cases/interview-debrief.md)
- [Skills](/agents/skills.md)
- [Campaign launch](/teams/marketing/use-cases/campaign-launch.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.