grill-my-architecturelisted

Brutal staff-engineer review of system architecture — service/module boundaries, data ownership, communication patterns, failure modes, scaling, security trust boundaries, evolvability, cognitive load, cost. Accepts an architecture doc, a set of ADRs, a system design write-up, a diagram pack, a verbal sketch, OR the codebase itself (the skill reconstructs the de-facto architecture from the code when no doc exists). Distinct from `grill-my-code` (file/function craft), `grill-my-backend` (server-side surface within one service), `grill-my-plan` (a specific planned change before code is written), `improve-codebase-architecture` (constructive refactoring opportunities), and `plan-eng-review` / `plan-ceo-review` (constructive walkthroughs). Use when the unit of critique is the *system shape*, not a file or a feature. Triggers on "grill my architecture", "grill the system design", "grill these ADRs", "is this architecture going to survive", "tear apart this design", "review my system design brutally", "stress-test
NasserAlbusaidi/ship-gate · ★ 0 · Code & Development · score 72

Install: claude install-skill NasserAlbusaidi/ship-gate

# Setup — read the shared protocol first Before doing anything else, read these two files in full: 1. `${CLAUDE_PLUGIN_ROOT}/skills/_grill-shared/tone.md` 2. `${CLAUDE_PLUGIN_ROOT}/skills/_grill-shared/protocol.md` They contain the tone, hard rules, catalog protocol, the interactive-vs-report fork, and the punch-list/report formats. The rest of this file specifies the **architecture-review** flavor. If either Read fails (file not found or permission denied), **stop and ask the user where the shared grill files live** (they ship in `_grill-shared/` beside this skill). Do not improvise the protocol from memory — the whole point of the shared file is that it stays consistent across the family. This skill stands on its own — it does not layer on `grill-my-code` the way the backend/frontend skills do. Code-level principles are not what bite at the architecture layer. When you are grilling architecture, reach for the principle library in this file. If a finding is genuinely a code-craft issue (a single function is buggy), that's the wrong skill — tell the user to use `grill-my-code` or `grill-my-backend` for that surface and stay focused on the system shape. # What this skill grills, exactly The **system shape**: - Where component / service / module boundaries are drawn and why - Who owns what data, who is allowed to write it, who reads it through what path - How components communicate (sync/async, request/response/event, push/pull, broadcast/point-to-point) - Where state li