← ClaudeAtlas

sprint-reviewlisted

Sprint review workflow — triage proposals, validate ticket readiness, and batch-promote tickets to dev. Load this before running a backlog review session.
Jessinra/Lorekeeper · ★ 2 · AI & Automation · score 72
Install: claude install-skill Jessinra/Lorekeeper
# Sprint Review Regular backlog review session to triage proposals, validate ticket readiness, and batch-promote validated tickets to dev. ## Cadence Run a sprint review **at least weekly**, or whenever there are enough proposals to triage. The goal is to keep the dev queue healthy — not to rush work. ## Process ### 1. Review all proposals Pull up all tickets in `S:proposal` status: ```bash cd ~/Code/lorekeeper ./scripts/lorekeeper-backlog.sh proposal ``` For each proposal, ask: - **Is the problem still valid?** — has anything changed since this was filed? - **Is the solution still the right one?** — any new context that changes the approach? - **Is the ticket complete enough?** — clear problem statement, acceptance criteria, affected files? ### 2. Validate readiness (the critical step) **Before promoting any ticket to `S:ready`, verify:** - [ ] **Problem still exists** — not solved by another change, not obsolete - [ ] **Solution still makes sense** — not superseded by a better approach since filing - [ ] **Acceptance criteria are concrete** — each AC is verifiable, not vague - [ ] **Affected files listed** — backend paths + dashboard changes (or `_none_`) - [ ] **No open blockers** — dependencies are listed and resolved - [ ] **Priority still correct** — not over/under-prioritized relative to other active tickets - [ ] **No duplicate** — check the rest of the backlog for overlapping ideas If a ticket fails any check: update it, defer it (S:deferred), or cancel