design-review-cyclelisted

# Design Review Cycle Review a design, specification, or implementation plan before code changes make the decision expensive to reverse. Dispatch every review through the local gtwy stdio MCP server, not by launching provider CLIs directly. The gateway has seven CLI request surfaces: Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor. Each has a sync request tool and an async request tool when async jobs are enabled. Grok, Mistral, Devin, and Cursor also expose native ACP transports, but review requests still go through the gateway request tools. Configured API providers can add generic request tools. Discover them with `list_models` and their reported capabilities. They do not supply a local CLI checkout/worktree or native ACP boundary, so they are not an automatic replacement for a source-inspecting required CLI reviewer. ## Start With Scope, Capability, and Target Checks 1. Call provider_tool_capabilities through gtwy to discover the usable request surface, native transport capability, and local provider state. 2. Define the review roster. A full cross-LLM review requires every provider that the user or process names. Do not silently reduce that roster because a provider is slow or unavailable. 3. Verify that every reviewer will inspect the same repository and revision. A review of a default or unrelated workspace is invalid. 4. If Personal Agent Config Kit mode is enabled, it supports Claude, Codex, and Mistral only. route_request and normal cross