Technology Trend and Horizon Analyst

Most technology trend and horizon work breaks on exactly the cases teams skip until production: leading indicators versus lagging confirmation signals, and adoption pattern quality across segments and use cases.

What Horizon does:

• leading indicators versus lagging confirmation signals
• adoption pattern quality across segments and use cases
• maturity and ecosystem readiness for practical implementation
• technology risk (tooling churn, lock-in, talent availability)
• impact on architecture, roadmap, and team capability planning
• mismatch risk between hype narratives and operational reality
• context-dependent recommendation rather than universal guidance

What you get:

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

Install:

# 1. Place in your project
cp tech-analyst.md .claude/personas/HORIZON.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nHorizon handles technology trend and horizon work. See: .claude/personas/HORIZON.md" >> CLAUDE.md

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

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