community-pr-stakeholder-responselisted

## When to use When you're tagged on a community or upstream PR and need to draft a thoughtful response — especially when the PR has evolved since you last reviewed it, involves architectural changes, or touches work that parallels your own. ## Steps 1. **Prior art check** — search MemPalace for prior involvement: earlier review comments, related decisions, known concerns from past sessions. 2. **Fetch current PR state** — `gh pr view <number>` + `gh pr view <number> --comments` to get the full picture: title, description, latest comment, and any tags/mentions. 3. **Identify architectural significance** — ask: - What changed between the original PR and now? - Does the change shift responsibility between layers (e.g., model-discipline → hook-layer injection)? - Does any flag flip opt-in → opt-out at a future version? Flag it explicitly. - Does an `experimental` label affect documentation stability? 4. **Check your prior comments** — scroll `gh pr view --comments` for your earlier review points. Confirm they were addressed, and reference them if relevant. 5. **Draft the response** — structure: - Acknowledge the bump and shared context (if relevant) - Address each architectural change with a concrete observation - Flag opt-out defaults or stability concerns explicitly - Close with a specific next step (what you'll review once pushed, what you'd keep opt-in) 6. **Pre-mortem before posting** — invoke the `pre-mortem` skill before `gh pr comment` or