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

# Find transformation opportunities

> Rank the highest-leverage automation and transformation candidates across the index.

A platform lead, AI architect, or transformation owner asks where to focus next. This is the "spin up multiple agents to scan the entire process tree" use case — agents should fan out in parallel across the hierarchy.

## Example prompts

* "Find the highest-leverage automation opportunities in our P2P value stream."
* "Where in our close cycle should we focus next?"
* "Scan our org for duplicate invoice processing across geographies."

## End-to-end recipe

<Steps>
  <Step title="Confirm the workspace">
    Call [`list_accessible_workspaces`](/tools/workspace) and switch if needed.
  </Step>

  <Step title="Build the work queue">
    Call [`get_process_hierarchy`](/tools/process-index) — the whole tree, or filtered to the value stream of interest. The leaves become your work queue.
  </Step>

  <Step title="Fan out in parallel across leaves">
    For each leaf:

    * [`get_process_details`](/tools/process-index) — current version, steps, dependencies. Note step count, manual vs system steps, exception count.
    * [`get_process_observations`](/tools/observations-and-changes) — exception volume per process (default summary verbosity).

    <Tip>
      The MCP is stateless per call. There's no penalty for parallel reads — fan out aggressively.
    </Tip>
  </Step>

  <Step title="Hunt high-leverage patterns in the index">
    Call [`search`](/tools/entry-points) directly on the index with pattern queries: "manual approval", "duplicate entry", "data re-keying", "exception handling", "swivel-chair workflow". For each hit, [`fetch`](/tools/entry-points) the process to confirm the pattern is real, not just a name match.
  </Step>

  <Step title="Check process attributes">
    Inspect the `attributes` field already returned by [`get_process_details`](/tools/process-index) — "automation status", "system of record", "control level", or similar attributes that help rank candidates.
  </Step>

  <Step title="Confirm each top candidate">
    For each top candidate:

    * [`get_process_observations`](/tools/observations-and-changes) with `verbosity="full"` — confirm the deviation or manual pattern with concrete evidence.
    * Read the `dependencies` field already returned by [`get_process_details`](/tools/process-index) for a first cut at blast radius.
  </Step>

  <Step title="Synthesize a ranked candidate set">
    Process IDs, observation counts, dependency depth, similarity to known patterns, evidence trail.
  </Step>
</Steps>

## What to surface in the brief

* A ranked list of candidate processes
* For each: observation count, dependency depth, pattern signal
* Citable process IDs and observation timestamps
* Gaps where the workspace doesn't have enough evidence yet