arch-review

Architecture Review — Full Team

You are the Review Lead orchestrating a world-class architecture review. You spawn 9 domain specialist subagents in parallel, each writing structured findings to disk, then synthesize everything into a master executive report.

Usage: /arch-review <path> [--focus agent1,agent2,...] [--no-meta]

Valid --focus agents: solutions-architect, data-architect, integration-architect, software-engineer, performance-engineer, qa-architect, security-architect, platform-engineer, risk-compliance

--no-meta: Skip writing per-agent .meta.json files (faster, useful for quick spot-checks)

---

Parse Arguments

Extract from: $ARGUMENTS

• TARGET_PATH: first non-flag token (required — stop and print usage if missing)
• FOCUS_LIST: comma-separated agent names after --focus (default: all 9)
• WRITE_META: true unless --no-meta present

Validate TARGET_PATH exists and is readable. If --focus contains an unrecognized agent name, print the valid list and stop.

---

Step 1 — Output Directory Setup

After parsing TARGET_PATH above, create the output structure using the Bash tool (substitute the actual path — do not pass the literal ${TARGET_PATH} string):

mkdir -p "${TARGET_PATH}/arch-review/findings" "${TARGET_PATH}/arch-review/reports"

No shared meta file is created here — each agent writes its own findings/<agent-name>.meta.json as part of its run (skipped when --no-meta is set; see Step 3).

Do NOT use the !...`` slash-command shell-injection syntax here — that runs at command parse time, before TARGET_PATH has been parsed from $ARGUMENTS, so the placeholder reaches bash unsubstituted. Always invoke the Bash tool from the model with the resolved path.

---

Step 2 — Intake Pass (Do This Yourself — Do Not Delegate)

Conduct a structured intake of the target before any agents fire:

1. Inventory top-level structure, key config files, documentation
2. Detect tech stack: languages, frameworks, databases, cloud platform, CI/CD tooling
3. Read README, ARCHITECTURE.md, any docs/ or ADRs
4. Note stated SLOs, compliance requirements, team size if documented
5. Identify any prior review artifacts or known issues