---
description: Review report changes against Report Harness repository rules and docs.
---

# /review

## Preflight

- Read `/AGENTS.md`, `/docs/PRD.md`, `/docs/ARCHITECTURE.md`, `/docs/ADR.md`, `/docs/UI_GUIDE.md`, `/docs/RESEARCH_LOG.md`, `/docs/REPORT_DRAFT.md`, and `/docs/FEEDBACK.md` if they exist.
- Identify the changed report files, research logs, feedback files, or generated `phases/` artifacts that need review.
- If the user wants a delegated review, use the read-only custom agent `harness_reviewer` only when they explicitly asked for subagents.

## Plan

- State what evidence will be checked: brief alignment, research coverage, source quality, unsupported claims, feedback handling, generated phase files, and validation output if available.
- Prioritize factual support, source freshness, CRITICAL rule violations, and missing counterarguments over style commentary.

## Commands

- Invoke `$harness-review`.
- Use Codex built-in `/review` when the user specifically wants a review-style pass over the working tree or generated report artifacts.
- If validation is relevant, run `python scripts/validate_workspace.py` or explain why it was not run.

## Verification

- Confirm that every finding is tied to a file and an actual rule or report-quality risk.
- If no findings remain, say so explicitly and mention residual risks or missing evidence.

## Summary

## Result
- **Action**: reviewed Report Harness changes
- **Status**: success | partial | failed
- **Details**: findings, docs checked, and validation status

## Next Steps

- Suggest the smallest follow-up: fix the top finding, rerun validation, or execute a pending phase.