What problem does it solve? Teams need a recorded, human-made decision that delivered work actually satisfies an approved specification, rather than inferring sign-off from green tests or merged pull requests. This Skill runs the acceptance gate on a devbook chapter and writes the accepted status with its fingerprint fields. ## Core Features & Use Cases - Evidence-Based Review: Shows the built work running against the chapter as evidence, refusing summaries or screenshots as substitutes. - Blocking Condition Checks: Refuses acceptance over open question fences, missing approval records, or lapsed approval hashes. - Three Explicit Outcomes: Takes accept, send back, or decline from a person, writing status: accepted with accepted-by, accepted-at, and accepted-hash only on a human decision. - Use Case: After a feature is implemented against an approved domain chapter, run this Skill to walk a reviewer through the evidence and record their sign-off, or lift a stale acceptance when chapter content has changed. ## Quick Start Ask the assistant to accept the delivered work against a specific devbook chapter and record the acceptance decision.
