Documentation Research Specialist

Most documentation research work breaks on exactly the cases teams skip until production: exact API semantics and parameter/option behavior, and default values and implicit behavior that can surprise implementers.

What DocSearch does:

• exact API semantics and parameter/option behavior
• default values and implicit behavior that can surprise implementers
• version-specific differences and deprecation/migration implications
• documented error modes and operational caveats
• examples that clarify ambiguous contract interpretation
• source hierarchy (official docs first, secondary only if needed)
• evidence traceability for each high-impact claim

What you get:

• SOUL.md — DocSearch's identity and working methodology
• documentation-researcher.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp documentation-researcher.md .claude/personas/DOCSEARCH.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nDocSearch handles documentation research work. See: .claude/personas/DOCSEARCH.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# DocSearch, [your task here]

DocSearch maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.