Purpose: Fetch current documentation for external packages before implementation
Golden Rule: NEVER rely on training data for external libraries → ALWAYS fetch current docs
Process: Detect package → Check install scripts → Use ExternalScout → Implement
When to use ExternalScout (MANDATORY):
Training data is OUTDATED for external libraries. ALWAYS fetch current docs using ExternalScout before implementation.
Why:
Example:
Training data (2023): Next.js 13 uses pages/ directory
Current (2025): Next.js 15 uses app/ directory
Training data = broken code ❌
ExternalScout = working code ✅
Triggers: User mentions library | package.json deps | import statements | build errors
ls scripts/install/ scripts/setup/ bin/install* setup.sh
grep -r "postinstall\|preinstall" package.json
Read scripts if found: What does it do? Environment variables? Prerequisites?
task(
subagent_type="ExternalScout",
description="Fetch [Library] docs for [topic]",
prompt="Fetch current documentation for [Library]: [specific question]
Focus on:
- Installation and setup steps
- [Specific feature/API needed]
- Required environment variables
Context: [What you're building]"
)
Check: Version compatibility | Peer dependencies | Breaking changes
Verify: Package installs | Imports work | API calls match docs
User Request: "Build Next.js commerce w/ Drizzle"
↓
STEP 1: ContextScout → Search internal context
↓
Internal context found?
↓
YES → Use internal NO → Is it external library?
↓
YES → STEP 2: ExternalScout (MANDATORY)
↓
STEP 3: Combine internal + external → Implement
| Scenario | ContextScout | ExternalScout |
|---|---|---|
| Project coding standards | ✅ | ❌ |
| External library setup | ❌ | ✅ MANDATORY |
| Feature with external lib | ✅ standards | ✅ lib docs |
Do ✅:
Don't ❌:
external-libraries-scenarios.md - Common scenarios and examplesexternal-libraries-faq.md - Troubleshooting FAQ.opencode/agent/subagents/core/externalscout.md - ExternalScout agent