check-third-party-docs

# Third-Party Package Documentation Workflow

Provides decision framework for accessing documentation on specialized third-party packages using Context7 MCP tools and dependency-docs-collector agent.

## Decision Framework

### Use Context7 MCP Directly

For **quick, focused lookups** on specialized packages when you already know what to ask:

**Scenarios:**

- API syntax verification during coding
  - "Verify `zod.object()` schema syntax"
  - "Check `sharp.resize()` options"
- Single method/function lookup
  - "What are `bull` queue retry options?"
  - "How to use `react-hook-form` controller?"
- Specific "how to" for known package
  - "How to validate nested objects with `yup`?"
  - "How to pipeline commands in `ioredis`?"

**Usage:**

```typescript
// 1. Resolve package to Context7 library ID
resolve-library-id("zod", "validate nested objects with zod")

// 2. Query specific documentation
query-docs("/colinhacks/zod", "How to validate nested objects with zod schemas")
```

**When Context7 fails:**

- Package not in Context7 index → Fall back to dependency-docs-collector agent
- After 3 failed resolve attempts → Use agent for web documentation search
- Outdated version docs → Agent can fetch latest version-specific docs

### Use dependency-docs-collector Agent

For **comprehensive documentation gathering** when you need implementation guidance:

**Scenarios:**

#### 1. Adding New Library for Feature

User wants to implement a feature requiring a new dependency:

```
User: "I need to add background job processing to my Express API"
→ Agent: Research job queue libraries (bull, agenda, bee-queue)
→ Gather installation, Redis setup, queue configuration, worker patterns
→ Provide implementation plan with chosen library

User: "Add PDF generation to my Next.js app"
→ Agent: Fetch pdfkit/puppeteer docs
→ Installation, API usage, Next.js integration patterns
→ Example implementation with serverless considerations
```

#### 2. Migrating Between Libraries

User wants to rep