← ClaudeAtlas

review-archlisted

Review system boundaries and architecture tradeoffs; not line-level code review.
ValentinNikolaev/agent-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill ValentinNikolaev/agent-skills
# Architecture Review Assess the architecture of a named system, subsystem, or design decision. Report structural risks grounded in the system's actual goals and constraints. Do not edit code or create a report file unless requested. ## Route precisely - Use this skill when the question concerns system structure, ownership, dependency direction, integration topology, or quality tradeoffs. - Use `review-spec` when a proposed specification or revision is the primary artifact and the question is whether its design is sound. - Use `verify-impl` for requirement-by-requirement conformance of existing code to a spec. - Use `code-review` for correctness of changed lines and ordinary pull-request readiness. A changed architecture may warrant both reviews when explicitly requested, with separate scopes. - Use `plan-review` for an ordered implementation plan. ## Scope and economical inputs Own system boundaries, responsibilities, data/lifecycle ownership, failure isolation, operator walkthroughs for screen-changing designs, and architecture alternatives. Not my scope: requirement-by-requirement coverage and acceptance testability (`review-spec`), implementation step ordering and step-by-step worst-case timing/capacity arithmetic (`plan-review`), or line-level defects (`code-review`). Use supplied requirements and calculations as constraints rather than repeating those reviews; identify needed evidence without starting extra reviewers automatically. Accept `shared_context=PATH` con