planreviewlisted

# Plan Review Compare what shipped against the plan that was approved. Surface where the implementation drifted and what follow-ups that warrants. The review runs in a forked agent with a clean context. An implementing session accumulates a justification for every departure as it happens, so drift goes unseen from inside it. A reviewer handed only the plan and the diff judges the delta cold. That outside view is the point: re-emphasizing the same prompt in the implementing context would not substitute for it. ## Fork the Review Claude Code writes the approved plan to a file under `~/.claude/plans/` and injects that file's path into the session when plan mode exits. That file is the plan. Use the path already in this session's context. If none was injected, the session built against no approved plan and there is nothing to review: say so and stop. Dispatch a background `general-purpose` Agent. Never `fork`: a fork inherits this session's context and defeats the outside view. The agent starts clean and has no idea where this skill lives, so hand it absolute paths: the plan file, and the rubric `references/divergence.md` resolved against this skill's base directory (that directory is in your context). A bare relative path resolves against the repo root in the agent's context and misses. Tell it to: - read the plan file. - work out the base branch this change targets, then diff what shipped against it. The branch's open PR is authoritative (`gh pr view --json baseRefName -q