Ask for a reviewable artifact
Claude Code has a plan mode, but the exact UI and file location can change. Use its current official documentation for the session you are running. Before approving work, ask the agent to save a plan in your project as a .md file if it has not already produced a durable artifact. Do not assume a hidden plan file is part of your repository.
The Agent Review Pack is a fictional exercise. Compare plan-v1.md and plan-v2.md with review-checklist.md. The first plan deliberately leaves scope questions open; the revised version states what will change and how to check it. These documents are examples, not output from a real Claude Code session.
Review in a fixed order
- State the user goal in one sentence and compare it with the proposed scope.
- List files that may change and dependencies the plan assumes.
- Check what the plan calls success and what evidence would prove it.
- Note omissions and ask for a revision before approving implementation.
Separate “the plan is easy to read” from “the plan is correct.” A Markdown reader can help you navigate headings and links; it cannot validate a design by itself. Aero Markdown can reload an already open plan when it changes and has optional local hooks for Claude Code, but the Mac app is not publicly available yet. For a broader checklist, see what to review before approving a generated plan.