> ## 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.

# Deck review with the partner

> Collect the partner's comments on a deck and turn them into a fix list.

Partner reviews leave comments scattered across slides, and the fix list gets rebuilt by hand. Hops reads the deck in Google Drive, collects every comment and turns them into one fix list with owners.

<Info>
  **How it runs:** Ask Hops, with a skill so the output has the same format every time. No automation needed.
</Info>

## What it does

* **Collects every comment.** Hops reads all comments on the deck in Google Drive or Slides, including replies and resolved threads.
* **Groups by slide.** Comments are organized slide by slide so each owner sees only their part.
* **Separates storyline from data fixes.** Changes to the narrative are listed apart from number and chart fixes.
* **Flags new analysis.** Any comment that needs analysis the team has not done is marked so it gets scheduled, not forgotten.
* **Assigns the slide owner.** Owners come from the deck's authors or the team listed in Space context.

<Frame>
  <img src="https://mintcdn.com/hopsdocs/E03FYifT87c9QmFJ/images/use-cases/ps-deliverable-draft.gif?s=d2cf8fd76232a12d4305acf90f261104" alt="Google Drive connection, Hops read 31 comments on the Acme strategy deck in Google Drive and built a fix list" width="1440" height="810" data-path="images/use-cases/ps-deliverable-draft.gif" />
</Frame>

## Ask Hops

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

```text theme={null}
Turn the partner's comments on the Acme strategy deck into a fix list.
```

```text theme={null}
Which comments on the Globex deck need new analysis?
```

```text theme={null}
List the storyline changes only, slide by slide.
```

```text theme={null}
What is still open from the partner's review of the Northwind deck?
```

```text theme={null}
Draft a short note to the team summarizing what changes before the client meeting.
```

Example reply:

> Fix list from 31 comments on the Acme strategy deck:
>
> * 4 storyline changes on slides 3 to 7.
> * 12 data fixes; 3 need new analysis.
> * Owners assigned for each slide.

## What you get

* **A fix list in chat**, in the same thread, grouped by slide with an owner for each item.
* **A saved Doc or Table, when you ask for one.** Say "save this as a doc" or "put this in a table" and Hops writes it to **Docs** or **Tables** in the Space so owners can tick items off.

## Connections needed

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

<CardGroup cols={3}>
  <Card title="Google Drive" icon="google-drive" href="https://app.hops.ai/my-hops/connections">
    The deck and its comments (or Google Slides).
  </Card>

  <Card title="Slack" icon="slack" href="https://app.hops.ai/my-hops/connections">
    Sharing the fix list with the team.
  </Card>
</CardGroup>

## Set it up

<Steps>
  <Step title="Connect your apps">
    Connect Google Drive or Slides, and Slack, in **Connections**.

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

  <Step title="Pin the deck (optional)">
    Create a **client-acme** Space and pin the deck and storyline in Space context.

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

  <Step title="Add the skill">
    Give Hops these instructions:

    ```text theme={null}
    You turn deck comments into a fix list. Group comments by slide, separate storyline from data fixes, assign the slide owner and note which need new analysis.
    ```

    See [Build a skill](/docs/agents/build-a-skill).
  </Step>

  <Step title="Ask">
    Ask Hops in chat after each review. Ask again before the client meeting to see what is still open.
  </Step>
</Steps>


## Related topics

- [Explore use cases](/use-cases/overview.md)
- [Agencies & consulting](/teams/professional-services.md)
- [Customer deck](/teams/sales/use-cases/customer-deck.md)
- [Partner onboarding](/teams/operations/use-cases/partner-onboarding.md)
- [VC & PE](/teams/vc-pe.md)


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