doc-review evaluates any PM document — a PRD, a ticket, a project brief, a tech spec — and returns structured feedback with severity-rated issues and a smell test. You paste in the document (or point to a file), and the skill identifies what's missing, what's vague, and what would cause problems downstream if left unaddressed. It auto-detects the document type, so you don't need to specify format before running it.
PMs produce and review documents constantly, but the review rarely happens with the same rigor as the writing. Teams approve PRDs with undefined success metrics, ship tickets with no edge cases, and brief engineers against specs that leave out the most important constraints. doc-review applies a consistent quality bar — the one a strong senior PM would apply — to every artifact you run it against, without fatigue or politeness.
Day 2 uses the PRD you produced on Day 1 as input. That sequence is intentional — you see your own work evaluated by the same standard you'll hold all future documents to. After today, you'll know what questions to ask before you draft, not after.