sprint-reviewlisted

# Symphony Sprint Review Use this skill for sprint reviews and demo-prep artifacts. Pedro should be able to ask Codex directly; he should not need to open Claude and ask again. This is a review/artifact workflow, not an implementation lane. Do not let this skill pull a repo into Symphony-owned coding or issue lifecycle work. Use it only to prepare grounded review artifacts when Pedro explicitly asks for that artifact. ## Workflow 1. Ground the review window. - Use Pedro's requested dates, meeting, project, or issue scope. - If Pedro says "latest meeting", "last meeting", "newest meeting", or is continuing a meeting-review thread, the default scope is that meeting's follow-up items only. Do not expand to earlier sprint work unless Pedro explicitly asks for a broader sprint/history review. - If the latest meeting was mostly debugging, access setup, deployment triage, or operations, do not automatically use it as the stakeholder-demo anchor. Treat the previous substantive product meeting as the baseline when Pedro frames the review as "changes since then"; items already shown or accepted in that baseline meeting are excluded from demoable new work. - If missing, infer the smallest sensible recent requested window and state it. - Before rendering, state the chosen window in plain language and verify it does not include unrelated previous-meeting foundation work or baseline items that were already shown before th