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

# Choose a workflow

> Choose the shortest Entelligence setup path for code quality, AI-agent ROI, reliability, knowledge, automation, or cost control.

Choose the smallest workflow that proves value. Add products only when their data or action improves that workflow.

<CardGroup cols={2}>
  <Card title="Catch issues before merge" icon="code-review" href="/code-review/setup">
    Connect source control, enable one repository, and run a pull-request review.
  </Card>

  <Card title="Review before opening a PR" icon="terminal" href="/code-review/cli-review">
    Install the CLI and review your local Git changes.
  </Card>

  <Card title="Measure AI-agent ROI" icon="chart-line" href="/agent-insights/setup">
    Connect coding-agent activity, map members, and inspect efficiency, spend, and outcomes.
  </Card>

  <Card title="Reduce model spend" icon="coins" href="/model-router/setup">
    Enable a routing mode for a pilot group and compare savings against the displayed baseline.
  </Card>

  <Card title="Prevent recurring incidents" icon="shield-check" href="/code-reliability/overview">
    Map incident sources to repositories, investigate patterns, and monitor fixes.
  </Card>

  <Card title="Keep repository knowledge current" icon="book-open" href="/documentation/setup">
    Generate docs, configure sync, and export to the destination your team uses.
  </Card>

  <Card title="Get answers in Slack" icon="message" href="/ask-ellie/slack">
    Connect Slack, map users, add the bot to a channel, and test a grounded question.
  </Card>

  <Card title="Automate recurring updates" icon="clock" href="/automations/pulse">
    Schedule a Pulse for a channel or manager without building a custom integration.
  </Card>
</CardGroup>

## Common cross-product workflows

| Workflow                                               | Products and sources                                               |
| ------------------------------------------------------ | ------------------------------------------------------------------ |
| Standardize reviews across repositories                | Code Review, guidelines, learnings, repository Markdown context    |
| Turn production history into preventive review context | Code Reliability, Git provider, incident sources, Code Review      |
| Improve failed or repetitive agent sessions            | Agent Insights, member mappings, local or centralized agent traces |
| Connect AI spend to project outcomes                   | Agent Insights, project-management mapping, budgets and outcomes   |
| Send a weekly engineering summary                      | Ask Ellie, Pulse, Slack, connected Git and delivery context        |
| Investigate an incident from a terminal                | CLI, Incident Knowledge, observability and Git sources             |
| Route coding-agent sessions while preserving rollback  | Model Router, CLI, a pilot group, billing controls                 |
| Onboard engineers from current code                    | Documentation, AGENTS.md sync, Ask Ellie                           |

## Selection questions

Before enabling a workflow, answer:

1. What decision or action should improve?
2. Which sources contain the minimum required context?
3. Does the workflow only read, or can it write to a repository, ticket, channel, or billing system?
4. Which role owns setup and ongoing operation?
5. What exact output proves the workflow works?
6. How will you disable or roll it back?

## Next step

Use the [integration catalog](/integrations) to confirm sources, then follow the setup guide for your chosen workflow.