What problem does it solve? Line-level code reviews confirm whether code is correct, but they cannot answer whether a pull request should actually ship to users. This Skill evaluates PR and branch diffs against the stated intent of the issue, surfacing how user value changes (for better or worse) so a product manager can make a go/no-go merge decision. ## Core Features & Use Cases - User Value Assessment: Reads the diff and translates changes into before/after user experience impacts, covering both gains and trade-offs. - Intent Alignment Check: Compares the implementation against the issue or PR description to detect scope drift, over-delivery, or silent spec changes. - Structured Verdict Output: Produces a concise summary with a pass / conditional pass / fail judgment, severity-labeled concerns, and a triage table of good, questionable, and unexpected changes. - Use Case: Before merging a feature branch, run this Skill to confirm the change delivers the intended value, has no unannounced behavior changes users would notice, and is safe to release. ## Quick Start Review this pull request from a PdM perspective and tell me whether it is safe to merge and how it changes user value.
