What problem does it solve? Devbook chapters need a recorded, human-made approval decision before they become work, and that decision must be written consistently — with the approver, date, and content hash — while clearing stale review state and resolved annotations. ## Core Features & Use Cases - Approval gate: Shows the full chapter with open annotation fences (questions, flags, suggestions) and blocks approval while any open question remains. - Three explicit outcomes: Approve, revise (records change requests as annotations and sets review state), or decline (records nothing), with no default and no inferred approval from silence. - Stale approval handling: Detects content changes after approval via chapter-hash comparison and lifts lapsed approvals, including any dependent acceptance. - Use Case: A specification chapter has passed review and a tech lead says "sign off on this" — the skill presents the chapter and open notes, takes the decision, and writes status, approved-by, approved-at, and approved-hash in one change. ## Quick Start Ask the assistant to approve the devbook chapter at a given path, for example: approve the chapter docs/specs/checkout.md and record who signed off.
