# Multica Review Architect

> Architecture-design dedicated review framework. Called by ArchReviewer to professionally analyze Architect's technical design (soundness/extensibility/acceptance alignment/tech risk), output PASS/FAIL + fix list, report to Leader.

- Skill: `it235/multica-review-architect` (Agent Skill)
- Install (CLI): `npx skillmds@latest add it235/multica-review-architect`
- Raw SKILL.md: https://api.skillmd.com/api/skills/it235/multica-review-architect/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: it235 (https://skillmd.com/u/it235)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/it235/multica-review-architect

---


# Architecture Design Professional Review (ArchReviewer)

Structured professional review framework for **technical architecture design artifacts**. Called by `ArchReviewer`; reviews the design link `Architect` returns via `multica-artifact-architect`.

## When to use
- ArchReviewer receives a "review architecture design" dispatch from Leader.
- Entering a re-review round after design changes (check previous round's fix list item by item).

## Review dimensions (conclusion per item)
1. **Soundness**: layering, module boundaries, dependency direction clear; no over/under-design.
2. **Extensibility & maintainability**: cost of common future changes; obvious tech debt.
3. **Acceptance alignment**: line-by-line coverage of AC-/FR-/BR-; list gaps.
4. **Key technical risk**: performance, consistency, security, data boundaries identified with mitigations; unmitigated risk = blocking.
5. **Cross-end consistency**: contract boundaries with frontend/backend self-consistent, no conflict with UI/API artifacts.

## Output format
```
【Architecture Review】<design link>
Conclusion: PASS / FAIL
Blocking items (required on FAIL, each: rationale / involved point / fix direction):
- ...
Suggestions (non-blocking):
- ...
Previous fix-list check (re-review): resolved X / unresolved Y
Round: N / 3
```
Conclusion + fix list **reported to Leader**; don't modify design or notify Architect yourself.

## Boundaries
- Review only architecture design, not UI, requirements, code, or test cases.
- Don't replace Leader's generic gate (multica-verification skill).
- Still FAIL at round 3 → mark "escalate to human", hand to Leader, stop looping.