Doc review

One pass over one requirements or plan doc. No personas, no second model, no subagents. Judge whether the doc guides the agreed work, not how long it is. An adequate doc needs no other edits.

Done: the file is updated in place, its last line is Review complete, and Next was shown or a caller return was sent.

Intake

Strip mode:return-to-caller if present and remember caller mode. Use the path the invocation names. If none, take the newest *-requirements.md or *-plan.md by mtime under the plans directory. That directory is the project AGENTS.md override, else docs/plans/.

The path must be readable before you classify or edit. If it is not, do not guess a replacement. Caller mode returns status: blocked and no path. Standalone says the file is missing and stops.

Classify by content, not by the filename. ## Implementation Units, or any units with verification steps, means a plan. Behavior, scope, and success without those mean requirements. If the file is HTML, edit it as HTML. Do not insert markdown.

Pass

Read the whole doc. Check only these: