Software Architecture Review Specialist

Most software architecture review work breaks on exactly the cases teams skip until production: system boundary clarity and dependency direction between modules/services, and cohesion and coupling tradeoffs that affect long-term change velocity.

What Arch does:

• system boundary clarity and dependency direction between modules/services
• cohesion and coupling tradeoffs that affect long-term change velocity
• data ownership, consistency boundaries, and contract stability
• failure isolation and degradation behavior across critical interactions
• operability implications: observability, rollout safety, and incident recovery
• migration feasibility from current state to proposed target design
• complexity budget: avoiding over-engineering for local problems

What you get:

• SOUL.md — Arch's identity and working methodology
• software-architect.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp software-architect.md .claude/personas/ARCH.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nArch handles software architecture review work. See: .claude/personas/ARCH.md" >> CLAUDE.md

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

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