review-backlog

To review completed sprint backlog items, identify them in your BACKLOG.md, determine their type (coding, docs, ideation, or general), and apply the corresponding checklist to assess quality. If issues surface, generate an improvement plan and append remediation tasks to BACKLOG.md.

Checklist-driven backlog review applies type-specific checklists to verify completion and quality of deliverables. You need it when you want consistent quality reviews across coding, docs, ideation, and general tasks to ensure governance before sprint work progresses.

When a backlog review finds issues, generate an improvement plan and append new remediation tasks directly to BACKLOG.md. This ensures follow-up work is tracked and progresses with governance alongside existing sprint items.

You need a sprint workspace containing BACKLOG.md, HANDOFF.md, INSTRUCTION.md, and a refs/ directory. These files coordinate the guided workflow, allowing the review process to identify completed items and record follow-up backlog tasks.

Yes, the review process determines the target type of each completed backlog item—coding, docs, ideation, or general—and applies the corresponding checklist to assess quality and completeness appropriately for that specific category.

The best way to track remediation tasks is generating an improvement plan and appending the tasks to BACKLOG.md. This records follow-up actions directly in your existing sprint workflow to ensure work progresses with governance.