Architecture review

Skill DominikTobureto/awesome-grok-build/.grok/skills/architecture-review

Grok Build resources, reusable .grok/skills, AGENTS.md templates, hooks, prompts, and starter workflows.

Install

npx -y skills add DominikTobureto/awesome-grok-build --skill architecture-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Use for clean architecture, modular monoliths, hexagonal boundaries, service boundaries, data flow, dependency direction, ADRs, or large feature planning.

SKILL.md

1.8 KB, as published. Nobody here has run it

Architecture Review

Design the smallest architecture that can survive the next real change.

Grok Build Mode

Start in Plan Mode. Architecture work should not begin with edits.
Use subagents for parallel discovery:
- domain: core entities, use cases, invariants.
- data: persistence, schemas, migrations, ownership.
- interfaces: APIs, UI boundaries, jobs, integrations.
- risk: coupling, circular dependencies, deployment constraints.
Arena-style design: compare 2-3 architecture options and rank by reversibility, simplicity, and testability.
Human-in-the-loop: ask for approval before introducing new layers, packages, services, or dependencies.

Workflow

Clarify the product/job-to-be-done.
Map current modules and data flow.
Identify constraints: runtime, team, deploy, scale, compliance.
Propose options:
- minimal change;
- modular boundary;
- larger redesign if justified.
Recommend one path with migration steps.
Define tests and observability needed.

Architecture Rules

Prefer modular boundaries over premature microservices.
Keep dependency direction explicit.
Put business rules where they can be tested without infrastructure.
Avoid abstract factories/layers unless they remove real coupling.
Write an ADR for major choices.

Example Prompts

Use architecture-review. Compare clean/hexagonal/modular approaches for this feature and recommend the smallest reversible plan.

Map the current data flow with subagents, identify coupling risks, and propose an ADR before edits.