What problem does it solve? Developer guides for SDKs, CLIs, frameworks, and API platforms often ship with fabricated endpoints, unverifiable getting-started steps, or missing integration recipes, leaving developers unable to adopt the tool. This Skill acts as an independent acceptance gate that judges a finished or amended developer guide against a fixed 14-condition bar and returns a machine-parseable verdict with actionable findings. ## Core Features & Use Cases - 14-condition adoptability + accuracy checklist: Judges goal-organization, verifiable first success, concepts-before-recipes, scenario coverage, Diataxis mode separation, api-reference linking, sample accuracy, versioning, troubleshooting, and findability. - Amend-mode delta review: When a change request and changed upstreams are handed in, reviews only the delta plus a staleness sweep for samples calling removed or renamed capabilities. - Machine-parseable verdict output: Emits exactly VERDICT: approve or VERDICT: revise plus actionable findings naming the failed condition, location, and concrete fix. - Use Case: After authoring a developer guide for a new SDK, run this Skill with the guide plus the feature-spec and api-reference to decide whether it can ship to integrating developers or needs a bounded revision pass. ## Quick Start Use reviewing-developer-guide to judge the finished developer guide at docs/developer-guide.md against the handed-in feature-spec and api-reference, and emit the verdict with findings.
