← ClaudeAtlas

architecture-review-workflowlisted

Review MSA, modular-monolith, and multi-module boundaries by combining system architecture, application architecture, DDD, and code-topology evidence. Use for service decomposition, module extraction, dependency-direction, data ownership, integration contracts, or architecture changes that need boundary-by-boundary findings.
ch4570/vulpora · ★ 1 · Code & Development · score 67
Install: claude install-skill ch4570/vulpora
# Architecture Review Workflow Assess boundaries from deployed system to application module to domain model. Review only; do not perform a restructuring unless the user separately requests implementation. ## Exact dependencies Mandatory agents: - `architecture-reviewer` - `application-architect` - `domain-driven-design-reviewer` Conditional topology agent: - `code-cartographer` Do not replace an unavailable mandatory agent with generic reasoning. ## Cost-aware native routing Resolve portable profiles from the current runtime capability catalog immediately before dispatch. Use `code-cartographer=frugal/low` and the three mandatory architecture passes=`standard/medium` by default. Raise only the affected pass to `frontier/high` for a confirmed security/authority boundary, irreversible data ownership, or public-contract decision. Every native handoff uses `model_selection: explicit-native-override`; spawn with `fork_turns: none`, the exact resolved `model`, and exact `reasoning_effort`. Never inherit the primary model or reasoning setting. Record requested and runtime-reported models separately, and fail the pass on mismatch. Timeout, quota, authentication, or missing tools do not justify a larger model. ## Input contract Accept a repository, diff, architecture proposal, or selected services/modules plus deployment topology, module build graph, public APIs/events, persistence ownership, team ownership, runtime constraints, and target style when available. Derive only