architecture-reviewer

name	architecture-reviewer
description	Review architecture, module boundaries, interfaces, coupling, scalability, data flows, and technical risks.
version	1.0.0
since	2026-07-28
last_modified	2026-07-28
authors	["platform-engineering"]
stability	stable
min_platform_version	{"codex":"unknown","amazon-q":"unknown","antigravity":"unknown","auggie":"unknown","bob":"unknown","claude-code":"unknown","cline":"unknown","codebuddy":"unknown","continue":"unknown","costrict":"unknown","crush":"unknown","github-copilot":"unknown","gitlab-duo":"unknown","factory":"unknown","forgecode":"unknown","opencode":"unknown","openhands":"unknown","cursor":"unknown","roo-code":"unknown","kiro":"unknown","junie":"unknown","gemini-cli":"unknown","iflow":"unknown","kilocode":"unknown","kimi":"unknown","lingma":"unknown","pi":"unknown","qoder":"unknown","qwen":"unknown","windsurf":"unknown","ollama":"unknown"}
deprecated_since	null
replaces	null
supersedes	[]
changelog	[{"version":"1.0.0","date":"2026-07-28","change":"Initial generated production-ready SDLC / DevSecOps skill"}]

Architecture Reviewer

Purpose

Review architecture for module boundaries, service boundaries, coupling, cohesion, dependency direction, data ownership, resilience, security boundaries, and ADR-worthy decisions.

When to use

• A design, PR, or refactor changes architecture, module boundaries, or service boundaries.
• API contracts, shared libraries, data ownership, or deployment topology change.
• Scalability, resilience, runtime coupling, or security boundaries need review.
• Circular dependencies, layering violations, or unclear ownership are suspected.
• An ADR should be created or updated.

Operating model

1. Map components, modules, services, APIs, data stores, queues, and deployment units.
2. Verify dependency direction, layering, cohesion, and ownership boundaries.
3. Trace data flows and ownership across tables, topics, buckets, and integrations.
4. Review runtime coupling, fan-out, retry behavior, scalability, and cascading failure risk.
5. Identify decisions that deserve ADRs and distinguish architecture risk from style preference.

Spec-Driven Change Context

• Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.
• For non-trivial changes, prefer a checked-in change artifact or equivalent proposal/design/tasks record before implementation begins.
• Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.
• Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.
• During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.
• After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.
• If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal/spec/tasks outline instead of relying on chat-only intent.

Skill-Specific Review Scope

• Module boundaries, service boundaries, layering, coupling, cohesion, and circular dependencies.
• API contracts, interface stability, compatibility, and versioning.
• Data ownership, data flows, cross-boundary writes, and direct database access.
• Runtime and deployment coupling, scalability, resilience, retry storms, and fan-out.
• Security boundaries, trust boundaries, ownership, and ADR candidates.

Skill-Specific Checklist

• Identify architectural layers and verify dependency direction.