#47 PM skill: enforce Opus-only constraint for reviewer role

[Anonymous]

Originally created by: kumaakh

Problem

Code review requires the highest reasoning capability to catch subtle bugs, security issues, and architectural problems. Lower-tier models (Sonnet, Haiku, Flash) miss issues that Opus catches reliably.

Requirements

• PM skill should warn the user when a non-Opus model is assigned as reviewer
• When pairing doer↔reviewer, check the reviewer's LLM backend and surface a recommendation
• If no Opus member is available for review, warn the user — but proceed if they choose to continue
• Doer role can use any tier (Sonnet, Haiku, Flash, Opus) without warning
• User's choice is final — never block assignment, only advise

Rationale

Reviews are the quality gate — a missed issue in review propagates to production. The cost of using Opus for review is justified by the higher catch rate for security issues, logic errors, and architectural drift. But ultimately the user decides what tradeoffs to make.

[Anonymous]

Ticket changed by: kumaakh

• status: open --> closed