research-methodology

Gathering version-specific documentation involves scanning dependency files like package.json or Cargo.toml to detect library versions. The skill prioritizes official sources and extracts API signatures, setup steps, and best practices to generate a structured, citation-ready brief.

A structured research pack is a compiled brief containing API signatures, setup instructions, gotchas, and best practices. It is generated by assessing dependencies and prioritizing official docs with citations to provide verified information before coding.

Yes, you can fetch official docs for target APIs by analyzing package files. The skill detects dependencies and versions from files like requirements.txt, targets the official documentation, and delivers a structured output with API details and migration guides.

Verifying library versions and citations is best done by cross-referencing dependency files with official documentation and release notes. This approach prioritizes authoritative sources, preventing misinformed decisions and reducing rework during integration.

Dependency analysis matters because it identifies exact library versions and API signatures before coding begins. By prioritizing official docs and release notes, it reduces the risk of using deprecated methods and minimizes implementation rework.