documentation-research

To fetch and cite upstream documentation for external dependencies, run the documentation-research process during forge Phase 2 or before SDK/API integration. It automatically gathers current external facts and ensures they are grounded in fetched documentation with inline citations.

Research external API documentation before writing code against an external SDK, framework, or CLI, or whenever training data may be stale. Running this during forge Phase 2 ensures all external dependency facts are verified and cited before integration.

Automated dependency documentation research handles source citations by citing three to five verified facts per fetched source. It uses inline citations and generates ISO-8601 timestamped source files alongside a SUMMARY.md file to track all external facts.

The best way to ensure external SDK documentation facts are not stale is to fetch current upstream documentation directly. This process grounds all external facts in fetched sources with ISO-8601 timestamps, verifying accuracy before you write integration code.

Yes, you can use automated research to document external SDKs before writing integration code. It fetches current upstream documentation, verifies three to five facts per source with inline citations, and outputs a SUMMARY.md file to ground your code in accurate external facts.

When automating external dependency documentation research, expect that it focuses strictly on fetching and citing external facts for dependencies in scope. It does not replace internal codebase analysis and relies on upstream documentation being accessible to generate its ISO-8601 timestamped source files.