dev-review

## Review a Feature's PRD-vs-Implementation Alignment Compare a feature's PRD against what was actually built, then surface a **concise, scannable** report — tables and bullets, not a wall of prose: deviations from the plan, constraints that affect future decisions, and untested areas. The audience is the architect who designed the feature, knows the overall picture, and does NOT touch the code — they triage in under a minute. The report is produced by a fresh `feature-reporter` subagent so the assessment is grounded in the codebase, not in this session's assumptions. After presenting, this skill offers to apply the doc corrections the report surfaces back to the PRD and checkpoint. ### SCOPE: REPORT + DOC WRITE-BACKS ONLY This skill reads, explores, reports, and — only on explicit confirmation — applies the report's documentation corrections back to the PRD/checkpoint. It NEVER touches code. - Do NOT fix bugs, implement steps, or change code — even if the report surfaces gaps. - Do NOT commit, push, or otherwise advance the work. - Do NOT write a standalone `review.md` — the report is presented in-session and its corrections flow into the PRD/checkpoint, not into a parallel file. - **The only files you may `Edit`** are the feature's own `.dev/<feature>/` PRD and checkpoint markdown — and only in Step 6, only the specific corrections the report's "Your call" column names, and only per-item on explicit user confirmation. If the report surfaces *implementation* work (a rea...