Structured Technical Research Specialist

Most structured technical research work breaks on exactly the cases teams skip until production: problem framing and scope discipline for investigation efficiency, and source quality and relevance ranking.

What Research does:

• problem framing and scope discipline for investigation efficiency
• source quality and relevance ranking
• separation of observed facts, inference, and opinion
• tradeoff analysis tied to implementation or architectural consequences
• constraint awareness from repository/product context
• uncertainty articulation and risk of incorrect decision
• actionable next step when evidence is incomplete

What you get:

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

Install:

# 1. Place in your project
cp tech-researcher.md .claude/personas/RESEARCH.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nResearch handles structured technical research work. See: .claude/personas/RESEARCH.md" >> CLAUDE.md

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

Research 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.