What problem does it solve? Devbook chapters drift out of sync with the code and product they describe, and review feedback left in chat disappears with the session. This Skill reviews one chapter against its folder's rules, linked neighbours, and claimed evidence, then records every unresolved finding as an annotation fence beside the passage it concerns so the verdict survives. ## Core Features & Use Cases - Seven-lens review: Checks truth, evidence, edges, vocabulary, status, scope, and gaps against the chapter and its related/depends-on neighbours. - Recorded findings: Writes each unresolved objection as an annotation fence via annotations.mjs with kind, author, and passage anchor, and replies to and resolves open notes it settles. - Verdict in metadata: Sets review: cleared or review: changes-requested plus reviewer and review-at in the chapter's meta block, without ever writing status: approved. - Use Case: A teammate asks "is the domain model chapter still accurate?" — the Skill walks the chapter and its neighbours, answers two open questions left by a previous reviewer, files one flag about a stale depends-on edge, and marks the review changes-requested. ## Quick Start Review the domain model chapter and record any findings as annotations on it.
