---
title: "List Clarity Process Summaries"
method: GET
path: "/v2/teams/{teamId}/clarity-v2/processes/summaries"
tags: ["ClarityV2"]
---

# List Clarity Process Summaries

`GET /v2/teams/{teamId}/clarity-v2/processes/summaries`

Cross-process portfolio digest for every completed Clarity process on the team: per-process summary, SWOT, projected impact, and a step skeleton (role, system, and flow edges) — without step prose or source excerpts. Paginated (default 5, max 10). Use this to answer portfolio-wide questions in one pass; fetch a single process's full detail via getClarityProcessSnapshot only for the few that matter.

## Path parameters

- `teamId` string, required

## Query parameters

- `limit` integer
- `offset` integer
- `detail` 'skeleton' | 'summary'
- `include_current_steps` 'true' | 'false'

## Response `200`

Default Response

- object
  - `processes` object[], required
    - `id` string, uuid, required
    - `name` string, required
    - `status` 'draft' | 'collecting' | 'generating' | 'generating-current-process' | 'generating-transformation-proposal' | 'review' | 'complete' | 'generation_failed', required
    - `created_at` string, required
    - `updated_at` string, required
    - `current` object, required
      - `summary` string, nullable, required
      - `swot` object, nullable, required
        - `strengths` string[], required — Internal advantages of the current process — capabilities, resources, or design choices that work in its favour today. Phrase each as a short, evidence-backed statement. Example: "Bartenders know regulars by name, which keeps service personal during peak hours."
        - `weaknesses` string[], required — Internal limitations of the current process — gaps, inefficiencies, or fragile assumptions visible in how it runs today. Phrase each as a short, evidence-backed statement. Example: "Manual pour times balloon during rushes because there is only one tap."
        - `opportunities` string[], required — External openings the current process could exploit — adjacent automations, scale effects, or unmet needs surfaced by the captures. Example: "POS data could feed dynamic pricing for slow hours."
        - `threats` string[], required — External risks that could degrade the current process — regulatory, operational, technological, or human factors visible in the captures. Example: "New ID-check legislation will require staff to interrupt every order."
    - `proposal` object, nullable, required
      - `summary` string, nullable, required
      - `projectedImpact` string, nullable, required
      - `steps` object[], required
        - `id` string, required
        - `title` string, required
        - `role` string, nullable, required
        - `system` string, nullable, required
        - `nodeType` string, nullable, required
        - `nodeSubtype` string, nullable, required
        - `condition` string, nullable, required
        - `readiness` string, nullable, required
        - `targetSteps` object[], required
          - `stepId` string, required
          - `label` string, nullable, required
          - `isDefault` boolean, required
    - `roles` string[], required
    - `systems` string[], required
  - `total` integer, required
  - `limit` integer, required
  - `offset` integer, required

## Other responses

- `400` — Default Response
- `401` — Default Response
- `500` — Default Response

---

[API](https://skmtc.net/duvo/apis/duvo-public-api.md) · [All operations](https://skmtc.net/duvo/apis/duvo-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/duvo/duvo-public-api/revisions/dafcf3d868a9/schema)