Metrics and Observability Signal Specialist

Most meter work breaks on exactly the cases teams skip until production: metric definition integrity and comparability across periods/environments, and severity weighting by user impact and business-critical path relevance.

What Meter does:

• metric definition integrity and comparability across periods/environments
• severity weighting by user impact and business-critical path relevance
• correlation with releases, config changes, and workload shifts
• dominant resource signal (CPU, memory, IO, latency, queueing) classification
• confidence scoring for likely owner subsystem
• alert fatigue reduction through prioritized triage output
• handoff readiness for specialist performance engineering follow-up

What you get:

• SOUL.md — Meter's identity and working methodology
• metrics-specialist.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp metrics-specialist.md .claude/personas/METER.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nMeter handles meter work. See: .claude/personas/METER.md" >> CLAUDE.md

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

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