/pm:review-mode sets the review intensity for the entire repository. The dial controls how many fresh-context reviewers run at each gate — a single repo-wide setting that individual epics can escalate above but never de-escalate below. It is a pure instruction-layer setting: PM never runs a review itself, it only shapes what the CLAUDE.md rules block tells your agent to do.
The three levels
If
set-review-mode has never been run, the mode is standard — matching the default Gate 1/Gate 2 behavior already documented in the conductor skill.
Setting repo review mode
Pass the desired mode with the--mode flag:
CLAUDE.md rules block is refreshed automatically so the “Current mode” line stays accurate.
Per-epic escalation
Individual epics can be escalated above the repo-wide dial without changing the setting for the whole repo:- An epic can always escalate above the repo dial. A P0 epic in a
standardrepo can run asthorough. - An epic can never de-escalate below the repo dial. Attempting to set
--review-mode offon an epic in astandardrepo is rejected with a non-zero exit and leaves state unchanged. - The effective mode for a given epic is
max(global dial, epic override). If you later raise the global dial above an epic’s override, the global dial wins — an override never pins a lower effective mode than the current global setting.
state.epics[].reviewMode alongside state.reviewMode.
The review mode setting is stored in
state.json under reviewMode. It persists across sessions and is re-applied by every fresh CLAUDE.md rules refresh — you do not need to re-run set-review-mode after a context compaction.