Software Development
System Design Review
System Design Review turns architecture decisions material into a review report with a concrete system service-boundary responsibility map, design tradeoff and failure-mode review, and review architecture decision handoff. It is built for teams that need a usable draft artifact, not a broad summary with a familiar title. The skill asks for system diagram, service notes, or design proposal, runtime boundaries and dependency map, and latency, reliability, data, or ownership constraints up front, then organizes the output around system, design, review, architecture, and decisions. It is delivered with adapters for Claude Code, Codex, OpenClaw, and Antigravity so teams can use the same workflow across their preferred agent environment. System Design Review is scoped to the Architecture Decisions workflow and is distinct from adjacent catalog skills by producing this specific deliverable rather than a broad summary.
One-Time Purchase
$19.99
System Design Review — Sample Brief
Headline
Builds an architecture review package for system design review work, turning system diagram, service notes, or design proposal, runtime boundaries and dependency map, and latency, reliability, data, or ownership constraints into system service-boundary responsibility map, design tradeoff and failure-mode review, and review architecture decision handoff. For target repository module, the example focuses on a concrete review report: the evidence to use, the fields a reviewer can inspect, and the owner decision needed before the work leaves draft state.
Evidence Packet
| Input | Example | Status |
|---|---|---|
| system diagram, service notes, or design proposal | target repository module notes and excerpts | Provided |
| runtime boundaries and dependency map | Three representative examples from the current workflow | Reviewed |
| latency, reliability, data, or ownership constraints | Approval threshold and final reviewer | Confirm |
| decision owner and review forum | Architecture Decisions owner and downstream audience | Ready |
Review Focus
| Lens | What this skill must inspect | Why it matters |
|---|---|---|
| System | Evidence specific to system design review system / design / review | Keeps the artifact tied to the actual source packet |
| Design | The boundary between System Design Review and adjacent Architecture Decisions skills | Keeps this skill from absorbing neighboring workflows |
| Review | The final reviewer decision, rejection reason, or edit path | Gives the next owner a clear approval or edit path |
Acceptance Checks
| Check | Required evidence | Review action |
|---|---|---|
| System depth | Tie findings to user task, viewport or state, accessibility expectation, and handoff acceptance rule. | Keep, revise, or ask a targeted follow-up |
| Design boundary | Separate visual preference from usability, content, and accessibility defects. | Confirm this is not a renamed adjacent bundle skill |
| Review handoff | Include reproduction or inspection notes that design and engineering can verify. | Assign the owner decision before final use |
System Design Review Work Map
System Design Review focus areas
Draft Review Report
| System signal | System Service Boundary Responsibility Map | Design Tradeoff And Failure Mode Review | Review Architecture Decision Handoff | Design decision |
|---|---|---|---|---|
| System | system service-boundary responsibility map | design tradeoff and failure-mode review | review architecture decision handoff | Keep if source-backed |
| Design | system service-boundary responsibility map | design tradeoff and failure-mode review | System evidence is missing or contradicted. | Revise missing evidence |
| Review | Tie findings to user task, viewport or state, accessibility expectation, and handoff acceptance rule. | Separate visual preference from usability, content, and accessibility defects. | review architecture decision handoff | Assign owner decision |
Use now
System Design Review
Best when architecture decisions work needs a concrete review report.
Hold back
Missing evidence
Best deferred when a key input would change the artifact.
Reviewer note
The output is structured so an operator can validate the draft, edit the artifact, and hand it to the next owner without re-reading the entire packet. The final answer should label unknowns plainly and avoid inventing metrics, policies, quotes, or commitments.
This sample illustrates the skill's output format. The artifact reviewed is illustrative and should be validated against the real repository before implementation.
View full sample →
All sales final. No refunds on digital products.
Includes support for Claude Code, Codex, OpenClaw, and Google Antigravity in the same license.
Also in Architecture Decisions
Bundle price: $44. Compare this skill with the full workflow bundle or Pro access.
Best for
System Design Review is best for buyers who need repeatable system, design, review work packaged as a structured, review-ready deliverable.
Not ideal for
System Design Review is not a fully autonomous service, managed integration, or substitute for required human review in high-stakes workflows.
Included in this purchase
- Claude Code, Codex, OpenClaw, and Google Antigravity skill files.
- Setup guidance for the right adapter in your workspace.
- One-time license for the purchased skill version.
Setup
Plan for a short setup in the repository or workspace where the skill will run. Some coding familiarity helps for implementation-heavy outputs.
Related Skills
$19.99
One-time license
$19.99
One-time license
$19.99
One-time license
Future Updates
This purchase includes the current version of the skill. If you want future adapter updates — meaning compatibility and packaging updates as supported platforms evolve — plus new catalog additions included automatically, upgrade to Pro.