---
title: Get the technology and delivery-risk view
description: One CTO lens on architecture, security, reliability, and delivery risk in an Operate cycle.
url: https://openplanr.dev/docs/prompts/technology-risk-review
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/prompts/challenge-the-operating-review.md
  - https://openplanr.dev/docs/prompts/operate-review.md
  - https://openplanr.dev/docs/prompts/turn-findings-into-decisions.md
---

# Get the technology and delivery-risk view

One CTO lens on architecture, security, reliability, and delivery risk in an Operate cycle.

## Prompt

Claude Code:

```text
/cto-review Review technology and delivery risk in the current operating review, focusing on the payments migration.
```

If /cto-review runs another command, use /planr:cto-review.

Codex:

```text
$cto-review Review technology and delivery risk in the current operating review, focusing on the payments migration.
```

With the OpenPlanr plugin for Codex, use $planr:cto-review.

Cursor:

```text
@planr-cto-review Review technology and delivery risk in the current operating review, focusing on the payments migration.
```

Cursor applies the planr-cto-review rule when you mention it in chat.

Parts to fill in, shown with their example text:

- The Operate cycle: the current operating review
- The area to focus on: the payments migration

## Why this works

The CTO lens is read-only. Each risk it raises names likelihood, impact, exposure, and reversibility, and keeps observed failures apart from inferred future risk. It does not present architectural preference or generic technical debt as business risk.

## Make it stick

[Track delivery and run operating reviews](https://openplanr.dev/docs/guides/operate.md)