Technical design review

When to use

Pressure-test an architecture or design doc before you commit. Multi-model review catches blind spots a single reviewer (human or model) misses.

Recommended setup

You are a senior staff engineer reviewing a technical design. Here is the design:

{PASTE DESIGN DOC}

Evaluate it for correctness, scalability, failure modes, security, operational complexity, and cost. List concrete risks ranked by severity, propose mitigations, call out anything missing, and end with a clear ship / revise / reject recommendation and your reasoning.

API example

{
  "model": "openrouter/fusion",
  "messages": [
    {
      "role": "user",
      "content": "You are a senior staff engineer reviewing a technical design. Here is the design:\n\n{PASTE DESIGN DOC}\n\nEvaluate it for correctness, scalability, failure modes, security, operational complexity, and cost. List concrete risks ranked by severity, propose mitigations, call out anything missing, and end with a clear ship / revise / reject recommendation and your reasoning."
    }
  ]
}

A Fusion call bills as the panel + judge combined — estimate it with the cost calculator. how to call the Fusion API.