What problem does it solve? Engineers often make API and architecture decisions based on memory or outdated blog posts, leading to integration bugs and rework. This Skill grounds technical answers in authoritative primary sources — official documentation, specifications, and source code — and delivers a verifiable report with citations. ## Core Features & Use Cases - Source Hierarchy Enforcement: Prioritizes official docs, RFCs, vendor source code, and release notes over secondary blogs, with explicit labeling when only secondary sources exist. - Structured Research Report: Produces a markdown report with confidence level, constraints table, conflicts section, and recommendations that can be pasted into issues or ADRs. - Version-Aware Verification: Matches documentation and source tags to the project's locked dependency versions and checks deprecation notices. - Use Case: Before integrating Stripe webhooks, run this Skill to verify idempotency behavior, timeout defaults, and retry semantics against the official API docs, then feed the findings into a spec or architecture decision record. ## Quick Start Ask the agent to research how a specific API or library actually behaves using official documentation and produce a cited research report with a confidence level.
