reviewlisted

# Review — Feature Acceptance & Feedback Orchestrate structured review of completed features. Walk through For Review tickets in batches, collect user feedback or acceptance, create bug sub-tickets when issues are found, and manage the full acceptance flow into PRODUCT_SPECIFICATION.md. **Architecture:** `PRODUCT_BACKLOG.md` (For Review section) --> review batches --> feedback/accept --> `PRODUCT_BACKLOG.md` + `PRODUCT_SPECIFICATION.md` --- ## Mode Detection | Invocation | Mode | |---|---| | `/review` (no args) | **review-all** — review all For Review tickets | | `/review {ID}` | **review-one** — review a single ticket by ID | --- ## Mode 1: review-all ### Step 1: Read the Backlog Read `PRODUCT_BACKLOG.md` in the current project directory. If not found in cwd, look up the project via `~/.claude/ticket-takeaway/registry.json` and use the registered path. **Always read fresh — never use cached content.** ### Step 2: Collect For Review Items Parse the `## For Review` section. Collect all `###` entries. If no items found, report: "Nothing to review." and stop. **Full-page ticket view:** For a detailed look at any ticket before or during review, open `/{project_id}/tickets/{ticket_id}?tab=overview` in the browser. The Activity tab (`?tab=activity`) shows a timeline of decisions; the Runs tab (`?tab=runs`) shows agent run history. ### Step 3: Sort and Group 1. **Sort oldest first** — by numeric part of ID (e.g., B-5 before B-12) 2. **Group into review batches** by p