01 ▸ Workflow Position
Run Plan
│
▼
┌─────────────┐
│ review-work │ (ACTIVE)
│ Independent │
└──────┬──────┘
│
▼
[DONE]
02 ▸ When to use?
Immediately after Run Plan or Long Run is complete. Used when you need to independently verify: "Did the implementation strictly follow the plan?"
Key Triggers
"review the work""verify implementation""check if it's done according to plan"
03 ▸ How it works?
Core Principle: The Reviewer is Information Isolated. It evaluates only the results, not the implementer's intent.
Verification Process
- Load & Parse Plan: Read the plan file directly to extract goals and acceptance criteria.
- Inspect Codebase: Compare planned files vs actual files and detect residual artifacts (TODOs, etc.).
- Independent Test Run: Do not trust worker results; execute all tests directly.
- Verify Git History: Confirm the planned commit structure matches the actual log.
- Binary Verdict: Judge only as PASS or FAIL and generate a review document.
04 ▸ Why Isolate Information?
A Reviewer who sees the Worker's output is prone to bias, such as "the intent was good, so it passes." Information isolation is a mandatory mechanism to ensure fairness by verifying only results.
05 ▸ Hard Gates
Mandatory Rules
- Never accept execution context (logs, output).
- Read original plan files, not summaries.
- Execute all tests and verification commands directly.
- Verdict must be binary: PASS or FAIL.
- Save review results as a file in the specified path.
- This skill is Read-only. Do not fix discovered issues directly.