What problem does it solve? Teams using devbook chapters lose track of who owes the next move: which chapters await a named reviewer, which carry unresolved notes, which are cleared and waiting for approval, and which approvals went stale after content changed. This Skill scans every adopted devbook folder and reports one queue grouped by the person responsible. ## Core Features & Use Cases - Cross-folder review sweep: Reads meta and annotation fences across all adopted devbook folders (from .devbook/config.json or disk) without loading chapter prose. - State-based routing table: Sorts each chapter into one of eleven rows — stale approval, changes requested, awaiting review, unsigned approval, notes to sweep, and more — each mapped to who owes the next move. - Exact staleness detection: Compares approved-hash/accepted-hash fingerprints via chapter-hash.mjs, falling back to git line-range history only when no fingerprint exists. - Use Case: Before a sprint review, ask what is waiting on approval across the repository and get a grouped queue showing each pending chapter, its wait time, and its open notes verbatim. ## Quick Start Ask the assistant to show the review queue across the devbook folders, including stale approvals and whose turn it is.
