Improve Architecture: Review and Improve Code Architecture

🥷 Periodically clean design debt, keep code healthy.

Outcome Contract

• Outcome: Architecture improvement report with findings, priorities, and PRD alignment analysis
• Done when: All PRDs scanned, codebase analyzed, findings categorized with priorities and effort estimates
• Evidence: Collected code patterns, PRD analysis, architecture alignment assessment
• Output: Structured report with blocking/high/medium priority findings

Prerequisites

Read available domain context before starting. If any are missing, proceed without them and note the limitation in the report:

• CONTEXT.md — domain glossary (if missing: scan code naming conventions instead)
• docs/adr/ — architecture decisions (if missing: no historical decisions to check against)
• docs/prd/*.md — product requirements (if missing: report focuses on code patterns only, no PRD alignment analysis)