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

# Spec review

> Engineering comments in place; Hops revises the spec and keeps a decision log.

Spec comments pile up, answers get lost, and decisions are forgotten by the next review. Hops turns each comment into a proposed edit, routes open questions and keeps a decision log.

<Info>
  **How it runs:** Scheduled. An automation runs every weekday at 5pm, posts open spec questions and updates a Table. You can also ask Hops any time.
</Info>

## What it does

* **Turns comments into edits.** For each comment on the spec, Hops proposes one concrete edit.
* **Applies only what the PM accepts.** Nothing changes in the spec without approval.
* **Keeps a decision log.** A Table records decision, owner, date and status.
* **Routes open questions.** Unanswered questions go to the person who can answer them, with a link to the comment.
* **Reads the spec where it lives.** Hops works with Notion or Google Docs and links the Jira or Linear tickets.

<Frame>
  <img src="https://mintcdn.com/hopsdocs/E03FYifT87c9QmFJ/images/use-cases/pe-spec-review.gif?s=f9a33fa4e6ce2e9e1b677c9ed951f384" alt="Search filters spec pinned in Space context, Hops turned review comments into edits" width="1440" height="810" data-path="images/use-cases/pe-spec-review.gif" />
</Frame>

## Ask Hops

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

```text theme={null}
Review the comments on the Search filters spec and propose an edit for each.
```

```text theme={null}
Apply the edits I accepted to the Acme search spec.
```

```text theme={null}
Which open questions on the spec have no owner or answer?
```

```text theme={null}
Add today's decisions to the decision log with owners.
```

```text theme={null}
Show me the decision log for the Search filters spec.
```

Example reply:

> Search filters spec review:
>
> * 4 comments turned into proposed edits, awaiting your approval.
> * 2 open questions routed to Alex Kim.
> * 3 entries added to the decision log.

## What you get

* **A daily post.** At 5pm, open questions and their owners are posted in the Space chat or your Slack channel.
* **An updated decision log.** Decisions are added as rows to a decision log in **Tables** in the Space.
* **Answers on demand.** Ask Hops to review new comments or apply accepted edits at any time.

## Connections needed

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

<CardGroup cols={3}>
  <Card title="Notion" icon="book" href="https://app.hops.ai/my-hops/connections">
    Specs and comments (or Google Docs).
  </Card>

  <Card title="Google Docs" icon="file-lines" href="https://app.hops.ai/my-hops/connections">
    Specs and comments (or Notion).
  </Card>

  <Card title="Jira" icon="jira" href="https://app.hops.ai/my-hops/connections">
    Linked tickets (or Linear).
  </Card>

  <Card title="Linear" icon="plug" href="https://app.hops.ai/my-hops/connections">
    Linked tickets (or Jira).
  </Card>

  <Card title="Slack" icon="slack" href="https://app.hops.ai/my-hops/connections">
    Where open questions are routed.
  </Card>
</CardGroup>

## Set it up

<Steps>
  <Step title="Connect your apps">
    Connect Notion or Google Docs, Jira or Linear, and Slack in **Connections**.

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

  <Step title="Create the Space">
    Create a **product-eng** Space and pin the spec template and the current spec 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 run spec reviews. For each comment, propose one concrete edit. Apply only edits the PM accepts. Keep a decision log table: decision, owner, date, status. Route unanswered questions to the person who can answer them.
    ```

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

  <Step title="Schedule it">
    Create an automation that runs every weekday at 5pm. It posts open spec questions with their owners to the Space and updates the decision log in **Tables**.

    See [Automation](/docs/spaces/automation).
  </Step>
</Steps>


## Related topics

- [Explore use cases](/use-cases/overview.md)
- [Product & Engineering](/teams/product-engineering.md)
- [Artifacts overview](/artifacts/overview.md)
- [Company AI brain](/use-cases/company-ai-brain.md)
- [Docs](/artifacts/docs.md)


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