> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mira-app.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Built-in Workflows

> Three production-ready multi-step pipelines that ship with every MIRA installation.

<Note>
  Workflows are **fully functional** and ready to use. Since built-in skills are indicative, feel
  free to tune them as needed while we continuously roll out new built-in skills, configuration
  options, and quality improvements.
</Note>

MIRA ships with three built-in workflows. They are read-only and run on either reasoning engine. You can duplicate any built-in workflow to use it as a custom template.

<CardGroup cols={3}>
  <Card title="Research Report Pipeline" icon="search" href="#research-report-pipeline">
    Gathers context, critically analyses it, then produces a structured report.
  </Card>

  <Card title="Code Review Pipeline" icon="code" href="#code-review-pipeline">
    Code analysis, security audit, performance review, and a consolidated summary.
  </Card>

  <Card title="Document Deep Dive" icon="file-text" href="#document-deep-dive">
    Extracts key information, classifies the document type, and synthesises insights.
  </Card>
</CardGroup>

***

## Research Report Pipeline

| Step                        | Type     | Description                                                                                                      |
| --------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------- |
| 1 · Gather & Understand     | `prompt` | Extracts key facts, claims, data points, and context from the input.                                             |
| 2 · Critical Analysis       | `prompt` | Analyses themes, arguments, evidence, and gaps based on step 1's output (`{{prev_output}}`).                     |
| 3 · Write Structured Report | `prompt` | Produces a complete report: Executive Summary → Key Findings → Detailed Analysis → Recommendations → Conclusion. |

**Template variables used:** `{{input}}`, `{{prev_output}}`

***

## Code Review Pipeline

| Step                     | Type        | Description                                                                             |
| ------------------------ | ----------- | --------------------------------------------------------------------------------------- |
| 1 · Code Analysis        | `prompt`    | Reviews structure, patterns, and obvious bugs in `{{input}}`.                           |
| 2 · Security Audit       | `prompt`    | Checks for OWASP issues, injection risks, auth problems — ratings: HIGH / MEDIUM / LOW. |
| 3 · Performance Review   | `prompt`    | Identifies N+1 queries, memory leaks, and algorithmic inefficiencies.                   |
| 4 · Consolidated Summary | `transform` | Aggregates all findings into a prioritised, self-contained code review report.          |

**Template variables used:** `{{input}}`, `{{prev_output}}`

***

## Document Deep Dive

| Step                        | Type        | Description                                                                                      |
| --------------------------- | ----------- | ------------------------------------------------------------------------------------------------ |
| 1 · Extract Key Information | `prompt`    | Pulls main thesis, key data points, claims, notable quotes, and authors from `{{document}}`.     |
| 2 · Classify Document Type  | `condition` | Determines whether the document is primarily technical/scientific, routing accordingly.          |
| 3 · Synthesize Insights     | `prompt`    | Provides deep insights that directly answer the user's question with evidence from the document. |

**Template variables used:** `{{document}}`, `{{input}}`, `{{prev_output}}`

<Warning>
  Document Deep Dive requires at least one document to be uploaded and enabled in the session before
  running.
</Warning>

***

## Duplicating a built-in workflow

1. Press ⌘3 to open Workflows.
2. Click a built-in workflow card.
3. Click **⋮ → Duplicate**.
4. Give the duplicate a new name.
5. Edit any step to customise the pipeline.

<Note>
  Edit this page — [Open a pull
  request](https://github.com/satyendra2013/mira-app/edit/main/docs/features/workflows/built-in-workflows.mdx)
</Note>