Prompt · Operate
Stress-test an operating review
Have the challenger test the review's claims, alternatives, downside, and confidence.
/challenger-review Challenge the claims, alternatives, and downside in this month's operating review.$challenger-review Challenge the claims, alternatives, and downside in this month's operating review.@planr-challenger-review Challenge the claims, alternatives, and downside in this month's operating review.If /challenger-review runs another command, use /planr:challenger-review.
With the OpenPlanr plugin for Codex, use $planr:challenger-review.
Cursor applies the planr-challenger-review rule when you mention it in chat.
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.
Related prompts
Run a monthly operating review
7 executive lenses, one decision and action brief.
Get the technology and delivery-risk view
One CTO lens on architecture, security, reliability, and delivery risk in an Operate cycle.
Turn review findings into decisions
Synthesize an operating review into a prioritized decision queue and an action plan.