---
title: Stress-test an operating review
description: Have the challenger test the review's claims, alternatives, downside, and confidence.
url: https://openplanr.dev/docs/prompts/challenge-the-operating-review
updated: 2026-10-06
related:
  - https://openplanr.dev/docs/prompts/operate-review.md
  - https://openplanr.dev/docs/prompts/technology-risk-review.md
  - https://openplanr.dev/docs/prompts/turn-findings-into-decisions.md
---

# Stress-test an operating review

Have the challenger test the review's claims, alternatives, downside, and confidence.

## Prompt

Claude Code:

```text
/challenger-review Challenge the claims, alternatives, and downside in this month's operating review.
```

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

Codex:

```text
$challenger-review Challenge the claims, alternatives, and downside in this month's operating review.
```

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

Cursor:

```text
@planr-challenger-review Challenge the claims, alternatives, and downside in this month's operating review.
```

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

Parts to fill in, shown with their example text:

- The Operate cycle: this month's operating review

## Why this works

The challenger tests only claims that could change a decision: unsupported claims, a weak assumption repeated by several advisors, a missing alternative, or downside nobody named. It does not invent objections to look busy.

## Make it stick

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